![]() |
![]() |
#232 | |
"Victor de Hollander"
Aug 2011
the Netherlands
23·3·72 Posts |
![]() Quote:
![]() |
|
![]() |
![]() |
#233 | |
Jun 2012
32×7×47 Posts |
![]() Quote:
|
|
![]() |
![]() |
#234 |
"Victor de Hollander"
Aug 2011
the Netherlands
23×3×72 Posts |
![]()
C228_23827_53
[ (23827^53-1)/23826 ] factors as: Code:
p92 factor: 61752513205787150608818684710149111788113044641425284877726924514491192476968132377158624603 p136 factor: 6561007901320801162078995151916585252669936213149633212472981902877268348326801246295711121837026773411315005714143440635595414163657147 Factors uploaded to Factordb: http://www.factordb.com/index.php?qu...3-1%29%2F23826 (Truncated) log attached and at: https://pastebin.com/wUrWK7Y5 |
![]() |
![]() |
#235 |
Jun 2012
32·7·47 Posts |
![]()
Do you want more relations on this number? I think Greg has fixed the glitches within NFS@Home.
|
![]() |
![]() |
#236 |
Sep 2009
977 Posts |
![]()
Nope, I do not have a copy of the old C216_49852639_29 dataset either, only of the C215_46988659_29 dataset per https://mersenneforum.org/showpost.p...postcount=1627 .
Yup, the glitches have been fixed, WU generation has restarted on both queues and clients have restarted eating (new) files. crunching.php indicates more relations for C179_374xx231_19 than appear in the remdups output from https://mersenneforum.org/showpost.p...postcount=1616 , but we can expand the range further if needed ![]() Last fiddled with by debrouxl on 2018-09-14 at 14:36 |
![]() |
![]() |
#237 | |
Jun 2012
32×7×47 Posts |
![]() Quote:
Lionel, how about I setup a second run and you double check (and submit) it? ETA: I have created the job and queued it for sieving. Once we are sure it is correct, we should also delete the erroneous job version (#1355?) per Greg. Last fiddled with by swellman on 2018-09-15 at 00:28 |
|
![]() |
![]() |
#238 |
"Rich"
Aug 2002
Benicia, California
22718 Posts |
![]() Code:
p54 factor: 221035798267746846728320242514920255139661570169625573 p156 factor: 557104798347474413683504505128229637761607544074276768813873084256665951739453545415683157847681808602934259881490520967747564440070770914111174363860501109 |
![]() |
![]() |
#239 |
Sep 2008
Kansas
2×3×547 Posts |
![]()
No. At Q=300M for a 31-bit job we are at the point of diminishing returns. We would have to go back and see what Q ranges are missing and try to piecemeal the possible sporadic ranges. Not worth the effort. I will let it run. Plus, I am already nearing 5% completed.
|
![]() |
![]() |
#240 |
"Rich"
Aug 2002
Benicia, California
3·13·31 Posts |
![]()
Reserving 11611_144 on 14e.
|
![]() |
![]() |
#241 |
Sep 2009
977 Posts |
![]()
The poly for 49852639^29-1 (C216_49852639_29A) matches the one in
https://mersenneforum.org/showpost.p...postcount=1541 so it LGTM ![]() |
![]() |
![]() |
#242 |
May 2009
Russia, Moscow
2×33×47 Posts |
![]()
Reserving C162_785232_11446.
|
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
2018 15e post-processing reservations and results | fivemack | NFS@Home | 221 | 2019-01-04 13:08 |
16e Post Processing Progress | pinhodecarlos | NFS@Home | 8 | 2018-11-28 13:45 |
Crash doing large post-processing job | wombatman | Msieve | 22 | 2013-12-04 01:37 |
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 |