Msieve 1.53 feedback

[VBCurtis]

The log doesn't list the parameters chosen; if you chose some unusual parameters, you might really need more relations. If you have a linux environment, you could try filtering with the CADO tools, though that's surely a learning curve to figure out how to convert your present data/parameters into CADO-friendly formats.

Sometimes filtering fails from too many relations; there's a flag you can invoke to tell it to use only the first, say, 90M relations. Or, you could try building with target-density=120, as that extra filtering might magically cure the "too many relations" issue. Without knowing what large-prime bounds you used, it's not obvious to me whether you have too many relations or too few. If you used lpbr/lpba = 31, 130M-150M raw relations might be necessary; but 31lp would be an ununusal choice for this size GNFS job.
I did a GNFS146 wtih 30lp, needing 75M raw relations, and I'm pretty aggressive about choosing larger large-prime bounds than most others around here (meaning I doubt any program chose 31lp on your behalf).
If 70-80M rels were all you need, using target-density might fix it; if not, you may have to use the filtering flag about number of relations ask msieve for its flag list via msieve -h).

[jasonp]

It looks like the large dataset bug. There is what may be a fix in the latest SVN.

[henryzz]

Originally Posted by jasonp

It looks like the large dataset bug. There is what may be a fix in the latest SVN.

Especially if that bug is fixed it may be worth actually releasing 1.53 at some point. 1.52 is 2 years old now.

[Alfred]

Originally Posted by jasonp

It looks like the large dataset bug. There is what may be a fix in the latest SVN.

Thank you.


msieve 153 svn 988 is running on this c143 now.

[Alfred]

The same behavior.

log file is attached.

[Alfred]

Originally Posted by Alfred

The same behavior.

log file is attached.

I used the binary from

http://www.mersenneforum.org/showpos...5&postcount=34

[xilman]

Could a case be made for DEFAULT_TARGET_DENSITY being set to something higher than 70.0?

[Alfred]

TD was set to 120 (in the run with msieve 1.53 svn 988)

[xilman]

Originally Posted by Alfred

TD was set to 120 (in the run with msieve 1.53 svn 988)

We may be talking at cross porpoises. In the source code here:

pcl@anubis ~/nums/msieve-code/trunk $ svn update
Updating '.':
At revision 993.
pcl@anubis ~/nums/msieve-code/trunk $ grep DEFAULT_TARGET_DENSITY */*/*
grep: b40c/b40c/radix_sort: Is a directory
grep: b40c/b40c/util: Is a directory
grep: b40c/test/bin: Is a directory
grep: build.cuda.vc12/gnfs/gnfs: Is a directory
grep: build.cuda.vc12/msieve/gnfs: Is a directory
grep: build.cuda.vc12/sort_engine_sm20/b40c: Is a directory
grep: build.cuda.vc12/stage1_core_sm20/gnfs: Is a directory
grep: cub/cub/agent: Is a directory
grep: cub/cub/block: Is a directory
grep: cub/cub/device: Is a directory
grep: cub/cub/grid: Is a directory
grep: cub/cub/host: Is a directory
grep: cub/cub/iterator: Is a directory
grep: cub/cub/thread: Is a directory
grep: cub/cub/warp: Is a directory
gnfs/filter/filter.c:#define DEFAULT_TARGET_DENSITY 70.0
gnfs/filter/filter.c:	merge->target_density = DEFAULT_TARGET_DENSITY;
grep: gnfs/poly/stage1: Is a directory
grep: gnfs/poly/stage2: Is a directory
pcl@anubis ~/nums/msieve-code/trunk $

the default target density is 70.0. If you want it to be 120 then you must set it explicitly on the command line.

Personally I'd put the #define in filter.h but that's a different and entirely stylistic matter.

[Alfred]

Wed Jun 08 14:04:15 2016  setting target matrix density to 120.0

The log file contains that line, so TD=120 is valid.

[xilman]

Originally Posted by Alfred

Wed Jun 08 14:04:15 2016  setting target matrix density to 120.0

The log file contains that line, so TD=120 is valid.

Yes, we are talking at cross porpoises. You're referring to one particular run where the target density was specifically set to a (non-default) value of 120. I'm asking whether the default for all runs should be set higher than 70, which is what you get if you don't specify a value.