mersenneforum.org > YAFU Strange YAFU behaviour
 User Name Remember Me? Password
 Register FAQ Search Today's Posts Mark Forums Read

 2012-07-14, 02:13 #1 ThomRuley     May 2003 23×31 Posts Strange YAFU behaviour I was just running yafu 1.32 and put in the following command line while in yafu: factor((261673^19-1)/(261673-1)) What I was hoping for was that it would go through various types of factoring -- trial factoring, rho, p-1, p+1, ecm, then siqs. What happened? It went straight to siqs and did no other factoring that I could see. Also, I have yet to find any evidence of an output file. Can anyone help me figure out what happened? Thanks Thom
 2012-07-14, 02:21 #2 Dubslow Basketry That Evening!     "Bunslow the Bold" Jun 2011 40> fac: factoring 33087358909991677955631647785105282516865431197533714982880853005580653265295676938249187371037963 fac: using pretesting plan: normal fac: using tune info for qs/gnfs crossover div: primes less than 10000 div: found prime factor = 6803 fmt: 1000000 iterations rho: x^2 + 3, starting 1000 iterations on C94 rho: x^2 + 2, starting 1000 iterations on C94 rho: x^2 + 1, starting 1000 iterations on C94 pm1: starting B1 = 150K, B2 = gmp-ecm default on C94 fac: setting target pretesting digits to 28.92 fac: sum of completed work is t0.00 fac: work done at B1=2000: 0 curves, max work = 30 curves fac: 30 more curves at B1=2000 needed to get to t28.92 ecm: 30/30 curves on C94 input, at B1 = 2K, B2 = gmp-ecm default fac: setting target pretesting digits to 28.92 fac: t15: 1.00 fac: t20: 0.04 fac: sum of completed work is t15.18 fac: work done at B1=11000: 0 curves, max work = 74 curves fac: 74 more curves at B1=11000 needed to get to t28.92 ecm: 74/74 curves on C94 input, at B1 = 11K, B2 = gmp-ecm default fac: setting target pretesting digits to 28.92 fac: t15: 7.17 fac: t20: 1.04 fac: t25: 0.05 fac: sum of completed work is t20.24 fac: work done at B1=50000: 0 curves, max work = 214 curves fac: 214 more curves at B1=50000 needed to get to t28.92 ecm: 214/214 curves on C94 input, at B1 = 50K, B2 = gmp-ecm default ETA: 0 secc pm1: starting B1 = 3750K, B2 = gmp-ecm default on C94 fac: setting target pretesting digits to 28.92 fac: t15: 37.74 fac: t20: 11.23 fac: t25: 1.05 fac: t30: 0.07 fac: sum of completed work is t25.33 fac: work done at B1=250000: 0 curves, max work = 430 curves fac: 309 more curves at B1=250000 needed to get to t28.92 ecm: 309/309 curves on C94 input, at B1 = 250K, B2 = gmp-ecm default ETA: 1 seccc fac: setting target pretesting digits to 28.92 fac: t15: 99.54 fac: t20: 49.85 fac: t25: 7.23 fac: t30: 0.79 fac: t35: 0.07 fac: sum of completed work is t28.93 starting SIQS on c94: 4863642350432408930711693044995631709079146141045673229881060268349353706496498153498337111721 ==== sieve params ==== n = 95 digits, 316 bits factor base: 88816 primes (max prime = 2410783) single large prime cutoff: 313401790 (130 * pmax) double large prime range from 43 to 51 bits double large prime cutoff: 1963281845692011 allocating 9 large prime slices of factor base buckets hold 2048 elements using 32k sieve core sieve interval: 18 blocks of size 32768 polynomial A has ~ 12 factors using multiplier of 17 using SPV correction of 20 bits, starting at offset 31 using SSE2 for x128 sieve scanning using SSE2 for resieving 13-16 bit primes using SSE2 for 8x trial divison to 13 bits using SSE2 for poly updating up to 15 bits trial factoring cutoff at 100 bits ==== sieving in progress (1 thread): 88880 relations needed ==== ==== Press ctrl-c to abort and save state ==== 41 rels found: 41 full + 0 from 2418 partial, (252.74 rels/sec)^C Aborting... sieve time = 0.0000, relation time = 0.0000, poly_time = 0.0000 trial division touched 244976 sieve locations out of 4827119616 ***factors found*** P4 = 6803 ***co-factor*** C94 = 4863642350432408930711693044995631709079146141045673229881060268349353706496498153498337111721 This is with the -v verbose output, though you still should have seen a small portion of this... (and p+1 was removed recently, in 1.31 I think).
 2012-07-14, 02:34 #3 ThomRuley     May 2003 23×31 Posts Thanks. My non-verbose output agreed with that, at least where the lines were given.
2012-07-14, 02:53   #4
Dubslow
Basketry That Evening!

"Bunslow the Bold"
Jun 2011
40<A<43 -89<O<-88

3·29·83 Posts

Quote:
 Originally Posted by ThomRuley Thanks. My non-verbose output agreed with that, at least where the lines were given.
...Well then it did do all of the things you say it didn't. Mine did. Which lines exactly do you see?

 2012-07-14, 02:54 #5 ThomRuley     May 2003 24810 Posts BTW, where is the output file?
2012-07-14, 03:48   #6
Dubslow
Basketry That Evening!

"Bunslow the Bold"
Jun 2011
40<A<43 -89<O<-88

3×29×83 Posts

Quote:
 Originally Posted by ThomRuley BTW, where is the output file?
factor.log.

Code:
07/13/12 21:15:01 v1.32 @ Gravemind,
07/13/12 21:15:01 v1.32 @ Gravemind, ****************************
07/13/12 21:15:01 v1.32 @ Gravemind, Starting factorization of 33087358909991677955631647785105282516865431197533714982880853005580653265295676938249187371037963
07/13/12 21:15:01 v1.32 @ Gravemind, using pretesting plan: normal
07/13/12 21:15:01 v1.32 @ Gravemind, using tune info for qs/gnfs crossover
07/13/12 21:15:01 v1.32 @ Gravemind, ****************************
07/13/12 21:15:01 v1.32 @ Gravemind, rho: x^2 + 3, starting 1000 iterations on C94
07/13/12 21:15:01 v1.32 @ Gravemind, rho: x^2 + 2, starting 1000 iterations on C94
07/13/12 21:15:01 v1.32 @ Gravemind, rho: x^2 + 1, starting 1000 iterations on C94
07/13/12 21:15:01 v1.32 @ Gravemind, pm1: starting B1 = 150K, B2 = gmp-ecm default on C94
07/13/12 21:15:01 v1.32 @ Gravemind, current ECM pretesting depth: 0.00
07/13/12 21:15:01 v1.32 @ Gravemind, scheduled 30 curves at B1=2000 toward target pretesting depth of 28.92
07/13/12 21:15:02 v1.32 @ Gravemind, Finished 30 curves using Lenstra ECM method on C94 input, B1 = 2K, B2 = gmp-ecm default
07/13/12 21:15:02 v1.32 @ Gravemind, current ECM pretesting depth: 15.18
07/13/12 21:15:02 v1.32 @ Gravemind, scheduled 74 curves at B1=11000 toward target pretesting depth of 28.92
07/13/12 21:15:05 v1.32 @ Gravemind, Finished 74 curves using Lenstra ECM method on C94 input, B1 = 11K, B2 = gmp-ecm default
07/13/12 21:15:05 v1.32 @ Gravemind, current ECM pretesting depth: 20.24
07/13/12 21:15:05 v1.32 @ Gravemind, scheduled 214 curves at B1=50000 toward target pretesting depth of 28.92
07/13/12 21:15:46 v1.32 @ Gravemind, Finished 214 curves using Lenstra ECM method on C94 input, B1 = 50K, B2 = gmp-ecm default
07/13/12 21:15:46 v1.32 @ Gravemind, pm1: starting B1 = 3750K, B2 = gmp-ecm default on C94
07/13/12 21:15:48 v1.32 @ Gravemind, current ECM pretesting depth: 25.33
07/13/12 21:15:48 v1.32 @ Gravemind, scheduled 309 curves at B1=250000 toward target pretesting depth of 28.92
07/13/12 21:19:50 v1.32 @ Gravemind, Finished 309 curves using Lenstra ECM method on C94 input, B1 = 250K, B2 = gmp-ecm default
07/13/12 21:19:50 v1.32 @ Gravemind, final ECM pretested depth: 28.93
07/13/12 21:19:50 v1.32 @ Gravemind, scheduler: switching to sieve method
07/13/12 21:19:50 v1.32 @ Gravemind, starting SIQS on c94: 4863642350432408930711693044995631709079146141045673229881060268349353706496498153498337111721
07/13/12 21:19:50 v1.32 @ Gravemind, random seeds: 173847163, 1987770324
07/13/12 21:19:50 v1.32 @ Gravemind, ==== sieve params ====
07/13/12 21:19:50 v1.32 @ Gravemind, n = 95 digits, 316 bits
07/13/12 21:19:50 v1.32 @ Gravemind, factor base: 88816 primes (max prime = 2410783)
07/13/12 21:19:50 v1.32 @ Gravemind, single large prime cutoff: 313401790 (130 * pmax)
07/13/12 21:19:50 v1.32 @ Gravemind, double large prime range from 43 to 51 bits
07/13/12 21:19:50 v1.32 @ Gravemind, double large prime cutoff: 1963281845692011
07/13/12 21:19:50 v1.32 @ Gravemind, allocating 9 large prime slices of factor base
07/13/12 21:19:50 v1.32 @ Gravemind, buckets hold 2048 elements
07/13/12 21:19:50 v1.32 @ Gravemind, using 32k sieve core
07/13/12 21:19:50 v1.32 @ Gravemind, sieve interval: 18 blocks of size 32768
07/13/12 21:19:50 v1.32 @ Gravemind, polynomial A has ~ 12 factors
07/13/12 21:19:50 v1.32 @ Gravemind, using multiplier of 17
07/13/12 21:19:50 v1.32 @ Gravemind, using SPV correction of 20 bits, starting at offset 31
07/13/12 21:19:50 v1.32 @ Gravemind, using SSE2 for trial division and x128 sieve scanning
07/13/12 21:19:50 v1.32 @ Gravemind, using SSE2 for resieving 13-16 bit primes
07/13/12 21:19:50 v1.32 @ Gravemind, trial factoring cutoff at 100 bits
07/13/12 21:19:50 v1.32 @ Gravemind, ==== sieving started (1 thread) ====`

Last fiddled with by Dubslow on 2012-07-14 at 03:48

2012-07-14, 03:54   #7
bsquared

"Ben"
Feb 2007

41·83 Posts

Quote:
 Originally Posted by ThomRuley BTW, where is the output file?
How are you running it? Unfortunately, managing where files go is something I still need to work on more. If you are running from the command line, and calling yafu from a different directory than where the executable sits, then some files will be next to the executable and others will be where you started it from. If you are running it some other way (double clicking on it, for example), then I think everything should be next to the executable.

 2012-07-14, 04:24 #8 ThomRuley     May 2003 23·31 Posts Thanks for your help. I found a workaround for the lack of an output file. The second factorization is much more verbose.

 Thread Tools

 Similar Threads Thread Thread Starter Forum Replies Last Post EdH YAFU 8 2018-03-14 17:22 ET_ Cloud Computing 15 2017-07-30 11:00 2147483647 YAFU 3 2016-12-25 21:44 LingUaan Software 13 2015-10-15 16:15 Cruelty Software 5 2008-06-12 21:23

All times are UTC. The time now is 02:40.

Mon Apr 12 02:40:47 UTC 2021 up 3 days, 21:21, 1 user, load averages: 2.34, 2.19, 1.86

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.