Problem with Msieve 1.50

[pgreenw]

I seem to be having a problem after the square root step. I am running msieve on linux.

-> ________________________________________________________________
-> | Running factmsieve.py, a Python driver for MSIEVE with GGNFS |
-> | sieving support. It is Copyright, 2010, Brian Gladman and is |
-> | a conversion of factmsieve.pl that is Copyright, 2004, Chris |
-> | Monico. Version 0.76 (Python 2.6 or later) 10th Nov 2010. |
-> |______________________________________________________________|
-> This is client 1 of 1
-> Running on 8 Cores with 4 hyper-threads per Core
-> Working with NAME = example3
-> Selected default factorization parameters for 131 digit level.
-> Selected lattice siever: gnfs-lasieve4I13e
-> Creating param file to detect parameter changes...
-> Running lattice siever ...
-> entering sieving loop
-> File 'deps' already exists. Proceeding to sqrt step.
-> Running square root step ...
-> ./msieve -s ../example/example3.dat -l ../example/example3.log -i ../example/example3.ini -nf ../example/example3.fb -t 32 -nc3
-> Computing 1.33753e+09 scale for this machine...
-> procrels -speedtest> PIPE
Traceback (most recent call last):
File "factMsieve.py", line 2104, in <module>
output_summary(NAME, fact_p, pols_p, poly_p, lats_p)
File "factMsieve.py", line 1787, in output_summary
(ret, res) = run_exe(PROCRELS, '-speedtest', out_file = subprocess.PIPE)
File "factMsieve.py", line 338, in run_exe
p = subprocess.Popen([ex] + args.split(' '), **al)
File "/usr/lib/python2.6/subprocess.py", line 633, in __init__
errread, errwrite)
File "/usr/lib/python2.6/subprocess.py", line 1139, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory

[schickel]

Originally Posted by pgreenw

I seem to be having a problem after the square root step. I am running msieve on linux.

It's not actually a problem with msieve, it's a problem with the Python script, though it's not really a problem with the script, either.....

-> procrels -speedtest> PIPE

I think you'll find this line is the problem.

The original automation script distributed with GGNFS ran a speed test to calcualte the scaling factor after a run. The speed test uses one of the filtering tools included with the original GGNFS suite. Check and see if you have a procrels.exe in the binaries folder. If not, you can either put a copy in there or just comment out the call to procrels. (You can check with other users of the script to see if the speed test remains relevant....)