[QUOTE=wombatman;458877]Bayesian tool recommends the following: [CODE]3400 curves with B1 = 2.9e9[/CODE][/QUOTE]

I'll take them.

C195 @ i2180
 

When the GNFS poly is needed please send me a PM.

ECM is almost done.

Is this series ready for GNFS? Appears to have sufficient ECM applied but just verifying.

This will be a big factoring job but certainly no longer cutting edge.

Ready for poly select, then? I can aim a GPU at it for the next ten days. Since I will likely not be the only one trying poly select, I'll leave the low ranges for others and start at 4M (likely to 7M or so).

[QUOTE=VBCurtis;472968]Ready for poly select, then? I can aim a GPU at it for the next ten days. Since I will likely not be the only one trying poly select, I'll leave the low ranges for others and start at 4M (likely to 7M or so).[/QUOTE]

I’m out of town right now but I will help search upon my return in 10 days. I’ll fill in gaps after others make reservations.

Let's first do a call for involvement?

Who is going to contribute sieving and how much can they do? How many cores, for how long.
Please check in below.

I can contribute 6 cores for 6 months.

I can put at least one Sandy Bridge quad core on it.

Though I had been assuming it would just go through NFS@Home. Is there any reason it couldn't?

[QUOTE=Dubslow;472987]Though I had been assuming it would just go through NFS@Home. Is there any reason it couldn't?[/QUOTE]

Likewise. GNFS-195 is definitely in 15e land on NFS@home. Serge's offer happens to be pretty close to the likely matrix-solving time.

However, we haven't done a forum-factoring collaboration project in quite a while. That's more fun, spirit of cooperation and all, but perhaps it's better used for numbers just above the reasonable 15e-queue range; say GNFS 197-200, or SNFS-290s.

I have an 8-core xeon with a sort-of-static IP at work that could host a forum-cooperative-CADO factorization. Such an effort is fully automated; helpers just point the cado-slave executable at the server IP/port, and work is issued automagically. Workunit length can be set fairly short, and cores can come and go as they please. Before doing such a thing, I would want some willing forumites to help me speed-test CADO vs lasieve, to make sure CADO isn't more than 10-12% slower. CADO thinks a G195 should be done with 3 large primes on one side, 32/33LP, and 15e; pretty close to what we'd have NFS@home do.

The server has 32GB, so it could (probably) handle the matrix at the end, though it would take 6-8 months.

Nfs@home can easily sieve 160M Q values per day for the 15e siever.

I also envisioned (somewhat arrogantly I see now) a large NFS@Home15e job once the poly was decided, but I’ll help on a group effort if we go that way. I’ll throw a quad core Sandy Bridge-ish at it (or point it at VBCurtis’ rig) until sieving is complete.

LA of course will be the biggest challenge.