CADO NFS - Page 45

EdH · 2020-08-28, 16:14

Quote:

Originally Posted by EdH

. . . More later.

The more:

There is an incompatibility barrier that was crossed sometime in March 2020 that causes WUs to fail across the barrier. This means that the server and clients need to be on the same side of March 2020.

Currently, there is an open issue that causes an Error -6 interruption on rare occasions. When this error occurs, CADO-NFS cannot complete filtering and won't move on. However, I have been able to run Msieve on the relations found, and even rerun CADO-NFS to add relations by using "tasks.sieve.rels_wanted" in the snapshot file and using the snapshot to restart the CADO-NFS run. It still failed at filtering in my tests.

RichD · 2020-08-28, 17:35

So upgrading everything to the above "commit" should be fine, whether server, client or standalone.

VBCurtis · 2020-08-28, 17:47

Quote:

Originally Posted by RichD

So upgrading everything to the above "commit" should be fine, whether server, client or standalone.

Except for the sometimes-broken filtering..

RichD · 2020-08-28, 17:52

Quote:

Originally Posted by EdH

Currently, ...

Quote:

Originally Posted by VBCurtis

Except for the sometimes-broken filtering..

Ah, yes.

EdH · 2020-09-07, 19:12

Just thought I'd post some more about the latest commit I'm using, since I mentioned the error (exit -6) trouble.

I'm still running the same commit across my entire "farm." I have only experienced one or two more of the troublesome error, but the bulk of my factorizations have been for composites <160 dd.

I have experienced a couple other issues, but they may have been noticed with earlier commits, too. The most annoying is if I run the server without the "--server" switch, quite often, one or more of the localhost polyselect processes gets lost. Then the server stops everything (except the constant checking for it) until the timeout occurs. It then goes ahead and reissues the WU and all is then well. But waiting an hour (or even the 15 minutes I now have it set at) for a lost WU to be replaced is (as mentioned) "annoying."

Because of this, I now use the "--server" switch and invoke the clients on the server machine externally.

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
CADO-NFS on windows	jux	CADO-NFS	22	2019-11-12 12:08
CADO help	henryzz	CADO-NFS	4	2017-11-20 15:14
CADO and WinBlows	akruppa	Programming	22	2015-12-31 08:37
CADO-NFS	skan	Information & Answers	1	2013-10-22 07:00
CADO	R.D. Silverman	Factoring	4	2008-11-06 12:35

2020-08-28, 17:35	#486
RichD Sep 2008 Kansas 110011001100₂ Posts	So upgrading everything to the above "commit" should be fine, whether server, client or standalone.

2020-09-07, 19:12	#489
EdH "Ed Hall" Dec 2009 Adirondack Mtns 2·1,811 Posts	Just thought I'd post some more about the latest commit I'm using, since I mentioned the error (exit -6) trouble. I'm still running the same commit across my entire "farm." I have only experienced one or two more of the troublesome error, but the bulk of my factorizations have been for composites <160 dd. I have experienced a couple other issues, but they may have been noticed with earlier commits, too. The most annoying is if I run the server without the "--server" switch, quite often, one or more of the localhost polyselect processes gets lost. Then the server stops everything (except the constant checking for it) until the timeout occurs. It then goes ahead and reissues the WU and all is then well. But waiting an hour (or even the 15 minutes I now have it set at) for a lost WU to be replaced is (as mentioned) "annoying." Because of this, I now use the "--server" switch and invoke the clients on the server machine externally.