20120504, 03:20  #34  
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 89<O<88
3×29×83 Posts 
Quote:


20120511, 23:40  #35 
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 89<O<88
3×29×83 Posts 
This is new
Code:
starting SIQS on c90: 529418472105108303888654672419843173237325298224814103927451866230400511694248308961680453 ==== sieve params ==== n = 91 digits, 302 bits (Edit: BTW, it says SSE2 all over the place; is that a function of the compiler, or...? How hard would it be to get AVX?) Last fiddled with by Dubslow on 20120511 at 23:42 
20120512, 00:40  #36  
"Ben"
Feb 2007
2^{2}·3·293 Posts 
Quote:
The SSE2 business is a function of the fact that I handwrote a lot of code utilizing SSE2 registers . I would have to rewrite all of those things in order to utilize AVX, and so far I haven't seen a clear benefit to that cost. 

20120512, 00:43  #37  
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 89<O<88
3·29·83 Posts 
Quote:
Attachment 7965 

20120512, 01:09  #38  
"Ben"
Feb 2007
2^{2}·3·293 Posts 
Quote:


20120512, 01:20  #39 
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 89<O<88
3·29·83 Posts 

20120513, 04:38  #40 
Mar 2006
479 Posts 
Hello bsquared, I think I may have run into a problem. I'm doing nfs on a number, and sometimes one of the sievers will crash, and then yafu says it has "Received signal 3". Then when all sievers have finished their range, yafu terminates. Is it possible to have it continue sieving even if one of the sievers had crashed during that last range? Here is a copy of what I'm seeing:
Code:
found 22916812 relations, need at least 44869961, continuing with sieving ... nfs: commencing algebraic side lattice sieving over range: 31243191  31323191 nfs: commencing algebraic side lattice sieving over range: 31163191  31243191 nfs: commencing algebraic side lattice sieving over range: 31083191  31163191 nfs: commencing algebraic side lattice sieving over range: 31483191  31563191 nfs: commencing algebraic side lattice sieving over range: 31803191  31883191 nfs: commencing algebraic side lattice sieving over range: 30843191  30923191 nfs: commencing algebraic side lattice sieving over range: 31323191  31403191 nfs: commencing algebraic side lattice sieving over range: 31643191  31723191 nfs: commencing algebraic side lattice sieving over range: 31403191  31483191 nfs: commencing algebraic side lattice sieving over range: 30763191  30843191 nfs: commencing algebraic side lattice sieving over range: 31563191  31643191 nfs: commencing algebraic side lattice sieving over range: 30683191  30763191 nfs: commencing algebraic side lattice sieving over range: 30923191  31003191 nfs: commencing algebraic side lattice sieving over range: 31723191  31803191 nfs: commencing algebraic side lattice sieving over range: 31003191  31083191♪◙ Warning: lowering FB_bound to 31643190. Warning: lowering FB_bound to 31403190. Warning: lowering FB_bound to 31803190. Warning: lowering FB_bound to 31163190. Warning: lowering FB_bound to 30683190. Warning: lowering FB_bound to 31243190. Warning: lowering FB_bound to 31083190. Warning: lowering FB_bound to 31723190. Warning: lowering FB_bound to 30843190. Warning: lowering FB_bound to 31323190. Warning: lowering FB_bound to 31483190. Warning: lowering FB_bound to 31003190. Warning: lowering FB_bound to 31563190. Warning: lowering FB_bound to 30923190. Warning: lowering FB_bound to 30603190. Warning: lowering FB_bound to 30763190. Special q 31643191 does not divide Received signal 3... please wait SCHED_PATHOLOGY q0=30952183 k=3025 excess=4 SCHED_PATHOLOGY q0=31466119 k=414 excess=4 total yield: 225921, q=31003199 (0.19416 sec/rel) total yield: 227093, q=31323203 (0.19403 sec/rel) total yield: 229532, q=31883191 (0.19248 sec/rel) total yield: 227840, q=31483213 (0.19488 sec/rel) total yield: 230264, q=30763207 (0.19326 sec/rel) total yield: 232742, q=31563193 (0.19267 sec/rel) total yield: 231013, q=31083193 (0.19469 sec/rel) total yield: 231129, q=31643191 (0.19484 sec/rel) total yield: 235153, q=31803197 (0.19413 sec/rel) total yield: 236249, q=31403249 (0.19330 sec/rel) total yield: 235944, q=31243193 (0.19397 sec/rel) total yield: 237541, q=31163191 (0.19342 sec/rel) total yield: 237676, q=30683203 (0.19404 sec/rel) total yield: 238889, q=30843199 (0.19396 sec/rel) total yield: 239558, q=30923197 (0.19439 sec/rel) Also, here is the command line I am using to start this job: Code:
yafu32kx64 "nfs(num)" R v threads 16 job c159.job o nfs.dat 
20120514, 16:08  #41  
"Ben"
Feb 2007
3516_{10} Posts 
Quote:
I see two things that can be done 1) I can ignore the exit condition of the ggnfs binary, which will solve your issue but will make it impossible (or at least much more difficult) to gracefully interrupt an ongoing factorization, or 2) attempt to learn all of the exit conditions of ggnfs on all supported OSes and build in the smarts to deal with various exit conditions. 1) does not sound very appealing and I don't have the time/willpower to do 2). I'm open to other suggestions. edit: What does factMsieve.pl/py do in this situation? edit2: maybe there is a way to issue the system calls in a nonblocking way so that yafu can retain visibility of an interrupt without relying on the exit condition of ggnfs... Last fiddled with by bsquared on 20120514 at 16:22 

20120515, 02:50  #42  
Mar 2006
111011111_{2} Posts 
Quote:
It looks like factmsieve.py usually expects a zero return value, but it also has a special case for the crash of the siever, like so: Code:
if ret and ret != 1073741819: output('> Return value {0:d}. Updating job file and terminating...' Also, while looking around for nonblocking system calls for Windows, about the only suggestion I could find was to try: Code:
system("start mycommand"); 

20120515, 04:42  #43 
"Ben"
Feb 2007
6674_{8} Posts 

20120516, 03:37  #44  
Mar 2006
479 Posts 
Quote:
Luckily I haven't had a siever crash on me in a long time, so I'm almost done factoring the C159. 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Running YAFU via Aliqueit doesn't find yafu.ini  EdH  YAFU  8  20180314 17:22 
Where to report bugs  Matt  Software  1  20070220 19:13 
Possible Prime95 bugs  JuanTutors  Software  9  20060924 21:22 
RMA 1.7 beta bugs  TTn  15k Search  2  20041124 22:11 
RMA 1.6 fixes LLR bugs!  TTn  15k Search  16  20040616 01:22 