![]() |
|
|
#507 |
|
Aug 2005
Seattle, WA
6E716 Posts |
Code:
p115 factor: 1375072630720284789051324709655982557102843920227765246576360792438490065794437358387280769130286355824187690407319 p129 factor: 455059745784478316142259547167242341234830262051360717067965347057276134401735567374794021211035081645418495098966573190103905447 |
|
|
|
|
#508 |
|
"Carlos Pinho"
Oct 2011
Milton Keynes, UK
3·17·97 Posts |
|
|
|
|
|
#509 |
|
Jun 2012
1100000101002 Posts |
Reserving 11p3_280.
|
|
|
|
|
#510 |
|
"Rich"
Aug 2002
Benicia, California
23×3×5×11 Posts |
Code:
p64 factor: 7172490328961059598644555453221468161433911810796225642370300169 p142 factor: 1029982188623040768022624086283627299853904524879016659220493647195767372857679545566992193606042980615935431227925878770745742633883712666297 Log attached and at https://pastebin.com/abtZ0Bbn Factors added to FDB. |
|
|
|
|
#511 |
|
Aug 2005
Seattle, WA
33478 Posts |
The 14e queue appears to be stuck. It's handing out WUs for C162_3366_2193, which doesn't exist on the status page (though C162_3366_2193a does). Does Greg need to be notified so he can cancel the bad WUs?
|
|
|
|
|
#512 |
|
Jun 2012
22·773 Posts |
Already dropped him a note. C162_3366_2193 was up briefly (3-5 minutes) but I killed it and started C162_3366_2193a later (difference was -r corrected to -a). It never was close to sieving but I guess it set up the WUs. One would think killing the job would stop the WU generation but I guess not.
|
|
|
|
|
#513 |
|
Aug 2005
Seattle, WA
6E716 Posts |
Taking 109xxx461_5m1.
|
|
|
|
|
#514 |
|
Aug 2005
Seattle, WA
3×19×31 Posts |
109xxx461_5m1 factored
Code:
p60 factor: 234800299026671155072646032031515458631011882292055207011861 p101 factor: 17233556909963256003389378286365914922607842149146256671371171644877474132020169377219543663600093381 Last fiddled with by jyb on 2019-07-20 at 12:48 |
|
|
|
|
#515 |
|
Sep 2008
Kansas
26·53 Posts |
Code:
p62 factor: 83334632014169877077500213198511794506450350088104453006708509 p135 factor: 133309208619144131767246762957318457746391502073800165897092397480819347701869326990834748884494775983680944548374447704295673875547199 Solve time about 243 hours. (-t 4) Log at: https://pastebin.com/p4JES5V1 |
|
|
|
|
#516 |
|
Jun 2012
22×773 Posts |
Code:
prp56 factor: 31713119845876619909815508590062079947631555975379014721 prp102 factor: 113378658196577638549673891339947450403088598817473888416342286254866997638391565544784886503090118561 |
|
|
|
|
#517 |
|
(loop (#_fork))
Feb 2006
Cambridge, England
23·11·73 Posts |
Code:
Sun Jul 21 00:51:57 2019 p122 factor: 47003457467621965332725155294368192990144278329705805255073899010025888755637380955081535748305115151279849830955357487009 Sun Jul 21 00:51:57 2019 p122 factor: 67408653841115853819581089585057198077681952582385931606079639606360232652115135971448486279121885417936384955744803244739 Last fiddled with by fivemack on 2019-07-21 at 07:04 |
|
|
![]() |
| Thread Tools | |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| 2018 15e post-processing reservations and results | fivemack | NFS@Home | 221 | 2019-01-04 13:08 |
| 2018 14e post processing reservations and results | pinhodecarlos | NFS@Home | 551 | 2019-01-04 13:06 |
| 16e Post Processing Progress | pinhodecarlos | NFS@Home | 8 | 2018-11-28 13:45 |
| Update on 7^254+1 post processing | dleclair | NFSNET Discussion | 4 | 2005-04-05 09:51 |
| Post processing for 2,757- | xilman | NFSNET Discussion | 3 | 2003-11-06 14:23 |