![]() |
[QUOTE=XYYXF;439256]I'll probably enqueue all t55 tasks to yoyo in September.[/QUOTE]
Nice. Though a full t55 is painfully slow on my hardware I will finish C178_140_114. ETA is 23 more days barring a hit. It's the the last C17X to be wrangled. Once all the t50 jobs are completed for this project, what is the next step? There are probably several possible paths, none being better than the others. Just curious. |
[QUOTE=swellman;439385]Once all the t50 jobs are completed for this project, what is the next step?[/QUOTE][QUOTE=XYYXF;439256]I'll probably enqueue all t55 tasks to yoyo in September.[/QUOTE]:)
|
Ah, so you mean ALL t55 tasks! I wrongly assumed you were referring to the table in the OP.
Factor on!:bow wave: |
Request C239_150_41 and C224_136_106 for 8k curves @11e7 be added to the table. Thanks.
|
Added.
All B1=110M tasks (except C178_140_114 which is reserved) will be done by yoyo very soon :) |
C178_140_114
Completed ECM to a full t55 with no factors found. I'll post it in the NFS@Home thread as a suggested 15e SNFS candidate.
|
C187_142_67:[code]7128360149039274062977936286065067193399002753241614879146717358452822451341395399593821536547721254531403479426890031997079861053249682361463634809511739986354847541601144102179145030773[/code]
and C202_134_87:[code]1224207612787772158727935698179132543695520938138955754343136473295556393880530309878400848872624432573326818957063965590308948460703802360355065604787211104932741174202689365592600945143938887378429707[/code] both survived t55 and need 5000 curves @300M. |
I'll take those two, it will take about five days and I can start in about a week.
|
5040@3e8 completed on C187_142_67; no factor found. About 5000 thread-hours.
5040@3e8 completed on C202_134_87; no factor found. 5361 thread-hours. I will do test sieving on both of these and queue up appropriately. |
I think C187_142_67 is a GNFS number: the SNFS difficulty is something like 268, the Murphy E score for the SNFS polynomial is 2.29e-14 and I've already found a 1.83e-14 GNFS polynomial after half a CPU-hour.
I am tempted at least to throw 1500 CPU-hours at the polynomial search and see what comes out; is that OK? The 15e queue is long enough that a few days delay is immaterial. |
[QUOTE=axn;451261]What is the SNFS poly that you used? The obvious deg-5 poly gives me 1.967e-014 (msieve 1.52 SVN 883).[/QUOTE]
SNFS difficulty 260 seems a bit high for a degree-5 polynomial. I used degree 6 and multiplied through by 67^2*142, giving [code] $ cat C187_142_67.snfs n: 7128360149039274062977936286065067193399002753241614879146717358452822451341395399593821536547721254531403479426890031997079861053249682361463634809511739986354847541601144102179145030773 skew: 0.1078 c6: 637438 c0: 1 Y0: 473338454265244805675008 Y1: -66956888672235945457062019127709902451882721 lpbr: 32 lpba: 32 mfbr: 64 mfba: 64 alambda: 2.6 rlambda: 2.6 alim: 240000000 rlim: 240000000 [/code] which has yield 1.10rel/Q and 0.63s/rel at Q=240M. |
| All times are UTC. The time now is 04:05. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.