2018 14e post processing reservations and results - Page 21

debrouxl · 2018-09-11, 06:35

The lss: line isn't there in the original polynomial from the near-repdigit Web interface, and as I wrote earlier in another topic, as long as the sieving side matches the usual recommended side implied by the type: line, the poly doesn't fail

All of the other recent GNFS polys which are still fully visible in the 14e management page have a lss: line, but multiple SNFS polys, such as #1442 13601_61_minus1, don't, and siever on the grid clients don't fail on these polys.

VictordeHolland · 2018-09-11, 09:21

C164_159978_10262 factors

Code:

p79 factor: 4766810075511487434911465766569047757783816417278851092890204825135327119935063
p85 factor: 4713139448874607477535005971654558298593994738547653012328478882915430001345704087049

7.2M matrix (TD=110)

Factors uploaded to Factordb.
(Truncated) log attached and at: https://pastebin.com/1xRf4PLm

VictordeHolland · 2018-09-11, 23:07

C215_46988659_29
(46988659^29-1)/46988658=

Code:

65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361

Is already in the Factordb:
http://www.factordb.com/index.php?id...00001060474966

It splits as:

Code:

p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537

So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).

RichD · 2018-09-12, 00:22

Quote:

Originally Posted by VictordeHolland

C215_46988659_29
(46988659^29-1)/46988658=

Code:

65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361

Is already in the Factordb:
http://www.factordb.com/index.php?id...00001060474966

It splits as:

Code:

p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537

So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).

It looks like I grabbed the wrong dataset when I did Phi_29(Phi_3(25457)/13). Can someone tell me the correct name for this job? I can't decipher it. It was just completed a couple days ago.

RichD · 2018-09-12, 00:40

Quote:

Originally Posted by RichD

It looks like I grabbed the wrong dataset when I did Phi_29(Phi_3(25457)/13). Can someone tell me the correct name for this job? I can't decipher it. It was just completed a couple days ago.

I found the queue request here but I don't remember seeing another dataset ending in _29.

debrouxl · 2018-09-12, 05:29

C217_69655517_29, or more probably C216_49852639_29 ?

VictordeHolland · 2018-09-12, 10:49

Quote:

Originally Posted by debrouxl

C217_69655517_29, or more probably C216_49852639_29 ?

C217_69655517_29
Shows as FF in the Factordb:
http://factordb.com/index.php?query=69655517%5E29-1

C216_49852639_29
Is still CF in Factordb:
http://factordb.com/index.php?query=49852639%5E29-1

RichD · 2018-09-12, 12:59

Quote:

Originally Posted by VictordeHolland

C216_49852639_29
Is still CF in Factordb:
http://factordb.com/index.php?query=49852639%5E29-1

That is the one that went by Phi_29(Phi_3(25457)/13) in the queue name. It shows completed as # 1355. Obviously, I grabbed the wrong dataset.

VictordeHolland · 2018-09-13, 23:42

Quote:

Originally Posted by RichD

That is the one that went by Phi_29(Phi_3(25457)/13) in the queue name. It shows completed as # 1355. Obviously, I grabbed the wrong dataset.

Does anybody got a copy of this dataset, I can't find it on the server?
Just to be sure: I'm looking for the relations of the C216 cofactor of 49852639^29-1 (the one that is displayed as factored but isn't) so we can clean this up.

Code:

 342979604182615255258693254421748108228322604383289993800565370414344839359283788981547172276819546740023979366342120920148747230565238271359993792909152771442330156630035414193369265772093168266608867254556175688641

RichD · 2018-09-14, 04:21

There doesn't seem to be any new relations coming in for C179_374xx231_19. Probably old WUs from previously submitted work that expired. I started this job building a matrix at TD=96 with just over 400 hours remaining.

RichD · 2018-09-14, 04:31

Quote:

Originally Posted by VictordeHolland

C215_46988659_29
(46988659^29-1)/46988658=

Code:

65434296264879485831057770993488700245967650017100071066373555801095079019465292289811876502805313831172779822893945904680867232753021773924258110416408044145755384753131700041017654832754227289103683721688682472361

Is already in the Factordb:
http://www.factordb.com/index.php?id...00001060474966

It splits as:

Code:

p106: 4672601456018195178699471914588665537722988275510203132077093911934729158719497712508274838757971243020753
p110: 14003825680574946026452519246879959936758227574144910522162981447781462580995284001498760348577141562692776537

So maybe somebody else already did the postprocessing and didn't post it in this thread (or I haven't noticed).

Victor should be credited with this job since he reserved and processed the job correctly. I will start the sieving locally (for the correct job) in a couple months since I am over subscribe at the moment.

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
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

2018-09-11, 06:35	#221
debrouxl Sep 2009 977 Posts	The lss: line isn't there in the original polynomial from the near-repdigit Web interface, and as I wrote earlier in another topic, as long as the sieving side matches the usual recommended side implied by the type: line, the poly doesn't fail All of the other recent GNFS polys which are still fully visible in the 14e management page have a lss: line, but multiple SNFS polys, such as #1442 13601_61_minus1, don't, and siever on the grid clients don't fail on these polys.

2018-09-12, 05:29	#226
debrouxl Sep 2009 977 Posts	C217_69655517_29, or more probably C216_49852639_29 ?

2018-09-14, 04:21	#230
RichD Sep 2008 Kansas 2²·3²·7·13 Posts	There doesn't seem to be any new relations coming in for C179_374xx231_19. Probably old WUs from previously submitted work that expired. I started this job building a matrix at TD=96 with just over 400 hours remaining.