new GNFS repunit 10,337- C202 target
 

[QUOTE=R.D. Silverman;538091]Here is a new GNFS target for everyone: A C202

6523 10,337- c268 906533749251005245151122204670351312590267105760052002862150546121.c202[/QUOTE]

Just to note, the recent GNFS repunit targets ~C200 were factored by Kurt Beschorner's team ([url]http://www.kurtbeschorner.de/[/url]) with polys selected with integrated knowledge of Mersenne Forum participants. It would be very nice for all of us to include Kurt in this discussion.

Max-
I'm not sure what you mean. It's an open forum, after all!

Repunit number
 

There are some special effort at repunit number (10^n - 1).

Kurt Team (Bo Chen, Wenjie Fang, Alfred Eichhorn, Danilo Nitsche, Kurt Beschorner, et al. ) aim at factoring

these number use snfs and gnfs, until last year we have polish most number snfs less than 300 and gnfs less than 200.

Now we are factoring snfs less than 310 and gnfs less than 210.

10,337- gnfs 202 is within our reach, I have suggest the team to factoring this number after the relation collect of

10^459 - 1, a snfs 306 number. In principle, we could factor this gnfs 202 with 12 months.

If Kurt and other members accept my suggestion, we will send Sam an email to reserve this number.

Yousuke Koide concentrates at 10^n+1, where n is between 400 and 800, using method ecm and nfs.

It would better if the duplicate effort could avoid.

If you still want to factor this number, we will not select this number as our next target.

I found 3,748+ c204 is also less than 210, perhaps you could factoring this number, I and Kurt have

no interest to this number.


Best regards,

Bo Chen

We can get the new C202 done by summer, and I'd prefer to not see it wait 12 months for a factorization.

If the C202 goes well, we are likely to try 3,748- the same way: with a combination of CADO work from forumites and nfs@home. We lack candidates of general interest between 200 and 205, so I would like to do the 202 to test this CADO-ggnfs hybrid rather than the 204 first.

2,2206M Factored by Yoyo
 

Yoyo found a p64. Nice work!

[QUOTE=swellman;541171]Yoyo found a p64. Nice work![/QUOTE]

May I suggest that 2,2230M be deleted from the YoYo queue? It is already sieving.

[QUOTE=R.D. Silverman;541841]May I suggest that 2,2230M be deleted from the YoYo queue? It is already sieving.[/QUOTE]

That’s unfortunate - I had private discussions with Greg about this issue and I thought 2,2230M would not start sieving until after Yoyo had run a round of ECM (likely by June).

If WUs for 2,2230M are now being distributed then I’ll ask Yoyo to remove the job from his queue.

[QUOTE=swellman;541850]That’s unfortunate - I had private discussions with Greg about this issue and I thought 2,2230M would not start sieving until after Yoyo had run a round of ECM (likely by June).

If WUs for 2,2230M are now being distributed then I’ll ask Yoyo to remove the job from his queue.[/QUOTE]

WU's are being distributed. Based on how long [elapsed time] it took for 2,2210M,
2,2230M will take about the same time to sieve that YoYo takes to do 12K curves.

[QUOTE=R.D. Silverman;541907]WU's are being distributed. Based on how long [elapsed time] it took for 2,2210M,
2,2230M will take about the same time to sieve that YoYo takes to do 12K curves.[/QUOTE]

BTW, 2,1115+ is the same difficulty as 2,2230M. It should be added to Greg's queue.

Think there’s less clients connected to NFS, 2,2230M will take longer.

And 2,2330M is underway at NFS@Home.