Go Back > Factoring Projects > Msieve

Thread Tools
Old 2012-05-20, 17:08   #1
May 2012

1 Posts
Default Problem with Msieve 1.50

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

-> ________________________________________________________________
-> | Running, a Python driver for MSIEVE with GGNFS |
-> | sieving support. It is Copyright, 2010, Brian Gladman and is |
-> | a conversion of 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 "", line 2104, in <module>
output_summary(NAME, fact_p, pols_p, poly_p, lats_p)
File "", line 1787, in output_summary
(ret, res) = run_exe(PROCRELS, '-speedtest', out_file = subprocess.PIPE)
File "", line 338, in run_exe
p = subprocess.Popen([ex] + args.split(' '), **al)
File "/usr/lib/python2.6/", line 633, in __init__
errread, errwrite)
File "/usr/lib/python2.6/", line 1139, in _execute_child
raise child_exception
OSError: [Errno 2] No such file or directory
pgreenw is offline   Reply With Quote
Old 2012-05-21, 03:42   #2
schickel's Avatar
"Frank <^>"
Dec 2004
CDP Janesville

2·1,061 Posts

Originally Posted by pgreenw View Post
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....)
schickel is offline   Reply With Quote

Thread Tools

Similar Threads
Thread Thread Starter Forum Replies Last Post
msieve SVN940 problem fivemack Msieve 11 2013-09-22 23:23
Problem in running msieve with CUDA mohamed Msieve 20 2013-08-01 08:27
Msieve: problem linking with other C library srawlins Msieve 6 2010-04-02 02:05
Problem compiling msieve with gcc 4.4.2 chris2be8 Msieve 5 2010-02-22 18:35
MSieve - problem with 106-digit effort schickel Msieve 5 2006-08-31 03:19

All times are UTC. The time now is 12:44.

Tue Oct 26 12:44:57 UTC 2021 up 95 days, 7:13, 0 users, load averages: 2.49, 2.84, 2.78

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.

This forum has received and complied with 0 (zero) government requests for information.

Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation.
A copy of the license is included in the FAQ.