Msieve 1.51 feedback

[xilman]

Originally Posted by chris2be8

That would be helpful. Ideally I would like to pass it the directory the .ptx files and the GPU sortlibs are in, and let it choose the right .ptx and sortlib for the GPU architecture from there. Eg pass it "gpudir=/home/chris/msieve-svn/trunk" and let it do the rest (obviously allowing for the sortlib being in the b40c subdir).

The dream is that if it isn't passed the parm it would look in the same dir msieve was in. So if my script calls it as /home/chris/msieve-svn/trunk/msieve it would look in /home/chris/msieve-svn/trunk for support files.

Chris

[aol]Me too !!!!????!!![/aol]

[VBCurtis]

Originally Posted by chris2be8

I assume that means to sort data_file_name.ms by the score in the last field. Will the number of fields in each record be constant? Does anyone have sample sort parameters to do this?

I assume that for large problems (over 155 digits) I need to run something like:
msieve -np1 -nps 1,50000 -g 0 (and other parms as necessary)
sort -k 9 msieve.dat.ms | head -100 >msieve.dat.ms.cut
mv msieve.dat.ms msieve.dat.ms.orig
mv msieve.dat.ms.cut msieve.dat.ms
msieve -npr
Chris

The number of fields is 5 more than the degree of the poly. Your initial trials may be small enough to be degree 4, which would explain your "-k 9" vs 10 that I've always sorted by for degree-5 problems up to ~200 digits.

I find that setting stage2_norm= {default/20 to default/22} produces a hit rate from -nps that is about right for the root optimization; 100 or so hits per day. This saves me the step of having to do the sort, and keeps the .ms file size smaller by a factor of 100 or more.

If you use the -s flag to create your own file names, you can avoid the mv commands; when you run -npr step with "-s sortedfile" also, it looks for sortedfile.ms automatically; so whatever you write as the sorted file name can be set as the input file for -npr.
-Curtis

[chris2be8]

Following a few tests I've found I need to use:

sort -g -k 10 msieve.dat.ms | head 100

The -g tells sort the key field is a floating point number. This might be worth putting into Readme.nfs.

Just to confirm, smaller score is better so I want the head of the sorted list, not the tail. (Always check the obvious!)

Chris

[jasonp]

Correct, the smaller size score is what you want.