YAFU 2.0 - Page 22

EdH · 2021-09-15, 23:09

Session:

Code:

YAFU Version 2.07
Built with GCC 9
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.0
Detected       Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz
Detected L1 = 32768 bytes, L2 = 15728640 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(1802716097522165018257858828415111497060066282677325501816640492782221110851604465066510547671104729)
fac: check tune params contained invalid parameter(s), ignoring tune info.
fac: factoring 1802716097522165018257858828415111497060066282677325501816640492782221110851604465066510547671104729
fac: using pretesting plan: normal
fac: check tune params contained invalid parameter(s), ignoring tune info.

yafu.ini tune info:

Code:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Tune options
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% If you run tune(), some information about the results should
% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
 tune_info=      Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz,LINUX64,2.98318e-05,0.19418,0.381544,0.1013,101.813,42

I've tried removing the prior info and I've tried removing the whitespace after the "tune_info=" and neither worked.

Thanks for all.

bsquared · 2021-09-15, 23:40

Quote:

Originally Posted by EdH

Code:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Tune options
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% If you run tune(), some information about the results should
% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
 tune_info=      Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz,LINUX64,2.98318e-05,0.19418,0.381544,0.1013,101.813,42

I've tried removing the prior info and I've tried removing the whitespace after the "tune_info=" and neither worked.

Thanks for all.

Try removing the space *before* your tune_info line :) It is apparently picky about leading spaces.

EdH · 2021-09-16, 00:38

Quote:

Originally Posted by bsquared

Try removing the space *before* your tune_info line :) It is apparently picky about leading spaces.

That space isn't actually there! It's an artifact that the board keeps throwing into "code" blocks! I'm always having to edit the &^%^$ things and I missed that one. This is the current block:

Code:

% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=      Intel(R) Xeon(R) CPU E5-2620 v2 @ 2.10GHz,LINUX64,3.08421e-05,0.193843,0.505431,0.0983408,101.613,42

Sorry for the bad data.*

2.03 doesn't proclaim bad tune data, but I can't tell if it's actually using any. I get the same output without current tune data:

Code:

YAFU Version 2.03
Built with GCC 9
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.1
Detected Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz
Detected L1 = 32768 bytes, L2 = 12582912 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(1802716097522165018257858828415111497060066282677325501816640492782221110851604465066510547671104729)
fac: factoring 1802716097522165018257858828415111497060066282677325501816640492782221110851604465066510547671104729
fac: using pretesting plan: normal
fac: using specified qs/gnfs crossover of 100 digits
fac: using specified qs/snfs crossover of 75 digits

starting SIQS on c100: 1802716097522165018257858828415111497060066282677325501816640492782221110851604465066510547671104729

Code:

% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=Intel(R) Xeon(R) CPU           X5650  @ 2.67GHz,LINUX64,2.52186e-05,0.196652,0.440998,0.0992702,100.318,42

I'll try updating that machine and I'll try building 2.07 on another very similar Xeon. (It might not be until tomorrow.)

* OF NOTE: The above block also added two characters, that I had to remove. I'm not seeing any extra characters in my gedit sessions. I've been experiencing this extraneous "junk" for a long time in all my code blocks. I don't think it's originating with me. I believe others have experienced the double returns and added characters in their code blocks, as well. But, I am open to all comments.

James Heinrich · 2021-09-16, 00:50

Quote:

Originally Posted by EdH

I've been experiencing this extraneous "junk" for a long time in all my code blocks.

Probable artifact of CRLF in an otherwise unix-style (LF-only) file? Does YAFU make any attempt to check whether new "tune" lines are being inserted into windows or unix style ini files, or does it always use one style (which?)

EdH · 2021-09-16, 02:40

Quote:

Originally Posted by James Heinrich

Probable artifact of CRLF in an otherwise unix-style (LF-only) file? Does YAFU make any attempt to check whether new "tune" lines are being inserted into windows or unix style ini files, or does it always use one style (which?)

I don't think the extraneous characters are anything to do with YAFU. They happen to me when I edit my posts to the board for all my scripts, too.

To be clear the yafu.ini file has no noticeable extra spaces or additional line termination as displayed by gedit and no extra spaces show up for my initial copy/paste to a message block. They only appear after I make a change somewhere in the post and review it. I can copy/paste a block of text and it shows up correctly, then preview and edit something and the extra character(s) show(s) up. I don't think it is my copy/paste because the artifacts don't show up immediately, only after editing within the board's window. But, I'm open to any thoughts.

Example test:

Code:

line one.
line two.
line three.
line four.

Code:

 line one edited.
  line two edited.
line three edited.
line four edited.

I typed the above two blocks directly into this message and both looked like the first one. Then I typed in the first edited and copy/pasted the other three. Now it has extra "junk."

Thanks for all suggestions.

EdH · 2021-09-16, 13:38

I had missed something earlier. The very first line I get is:

Code:

Applying tune_info entry for LINUX64 -        Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz

Then it shows the following messages. This is a second nearly identical machine to the previous one:

Code:

$ ./yafu
Applying tune_info entry for LINUX64 -        Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz


YAFU Version 2.07
Built with GCC 9
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.1
Detected        Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz
Detected L1 = 32768 bytes, L2 = 15728640 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(3895019629310942791127924868760001374161564829081811090059087663376519150666208901154051)
fac: check tune params contained invalid parameter(s), ignoring tune info.
fac: factoring 3895019629310942791127924868760001374161564829081811090059087663376519150666208901154051

Here are the last few lines of the tune operation:

Code:

nfs: estimated time for complete factorization = 31033.7059 seconds
best linear fit is ln(y) = 0.101147 * x + -0.891959
R^2 = 0.967072
best exponential fit is y = 0.409852 * exp(0.101147 * x)
QS/NFS crossover occurs at 100.3 digits
found OS = LINUX64 and CPU = Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz in tune_info field
Adding tune_info entry for LINUX64 -        Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz


***factors found***


ans = 0

and the last few of the new yafu.ini:

Code:

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Tune options
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% If you run tune(), some information about the results should
% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=       Intel(R) Xeon(R) CPU E5-2630 0 @ 2.30GHz,LINUX64,2.60097e-05,0.197536,0.409852,0.101147,100.272,42

No editing has been done to the yafu.ini file after running tune. The only editing prior, was threads and paths for ggnfs and ECM.

This entire message was constructed via gedit without editing anything via the board's tools.

James Heinrich · 2021-09-16, 13:41

If you think it's relevant, you might use the attachment feature of the forum to attach your .ini file to avoid any copy-paste-edit garbling.

EdH · 2021-09-16, 14:01

Quote:

Originally Posted by James Heinrich

If you think it's relevant, you might use the attachment feature of the forum to attach your .ini file to avoid any copy-paste-edit garbling.

A good suggestion! I'll wait a bit to see what b² may come up with and while I upgrade a couple more diverse machines. I'm upgrading another Xeon ATM. Then I'll try an i7.

EdH · 2021-09-16, 15:01

Well, no luck with these, either. Here's an i7 right after running tune:

Code:

$ ./yafu
Applying tune_info entry for LINUX64 -         Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz


YAFU Version 2.07
Built with GCC 9
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.0
Detected         Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz
Detected L1 = 32768 bytes, L2 = 8388608 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(1006937478603500243574011966177501282832467119633045794739218202437560443941866695322821)
fac: check tune params contained invalid parameter(s), ignoring tune info.
fac: factoring 1006937478603500243574011966177501282832467119633045794739218202437560443941866695322821
fac: using pretesting plan: normal
fac: check tune params contained invalid parameter(s), ignoring tune info.

i7's yafu.ini tune info:

Code:

% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=        Intel(R) Core(TM) i7-2600 CPU @ 3.40GHz,LINUX64,1.77913e-05,0.197298,0.28037,0.100998,100.365,42

Here's an AMD machine:

Code:

$ ./yafu
Applying tune_info entry for LINUX64 - AMD Phenom(tm) II X4 B95 Processor


YAFU Version 2.07
Built with GCC 9
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.0
Detected AMD Phenom(tm) II X4 B95 Processor
Detected L1 = 65536 bytes, L2 = 6291456 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(8115344633731779104344693675156365299077770243773155282218623609391019030239893061930191)
fac: check tune params contained invalid parameter(s), ignoring tune info.

and its tune info:

Code:

% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=AMD Phenom(tm) II X4 B95 Processor,LINUX64,1.5946e-05,0.202008,0.525842,0.0965283,98.6309,42

All of the previous machines were running Ubuntu 20.04.

Here's a Debian (Buster) machine:

Code:

$ ./yafu
Applying tune_info entry for LINUX64 - Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz


YAFU Version 2.07
Built with GCC 8
Using GMP-ECM 7.0.5-dev, Powered by GMP 6.2.0
Detected Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz
Detected L1 = 32768 bytes, L2 = 2097152 bytes, CL = 64 bytes
Using 1 random witness for Rabin-Miller PRP checks
Cached 664579 primes; max prime is 9999991

===============================================================
======= Welcome to YAFU (Yet Another Factoring Utility) =======
=======             bbuhrow@gmail.com                   =======
=======     Type help at any time, or quit to quit      =======
===============================================================

>> factor(2239620260486900894908265519196420231768486265882316440459029916618515194783127449405749)
fac: check tune params contained invalid parameter(s), ignoring tune info.

and its tune info:

Code:

% appear below here


tune_info=Intel(R) Xeon(R) Gold 5122 CPU @ 3.60GHz,LINUX64,1.59078e-05,0.196092,0.299688,0.0999245,102.36,42
tune_info=Intel(R) Core(TM)2 Quad CPU    Q8400  @ 2.66GHz,LINUX64,2.51073e-05,0.198206,0.473332,0.100239,100.487,42

Maybe it's me. . .

Thanks for all the help/suggestions.

EdH · 2021-09-16, 16:48

Just an additional note that the other Xeon acted the same. I forgot to include it in the last post.

James Heinrich · 2021-09-16, 17:04

I'll admit I'm posting this while looking at v1.34.5 and not v2.07, but is it possible to add in some kind of rough ETA to SIQS, which currently displays something like:

Quote:

==== sieving in progress ( 6 threads): 144224 relations needed ====
==== Press ctrl-c to abort and save state ====
41708 rels found: 20823 full + 20885 from 1252184 partial, (622.51 rels/sec)

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
yafu ignoring yafu.ini	chris2be8	YAFU	9	2022-02-17 17:52
Running YAFU via Aliqueit doesn't find yafu.ini	EdH	YAFU	8	2018-03-14 17:22
YAFU-1.34	bsquared	YAFU	119	2015-11-05 16:24
Yafu bug.	storflyt32	YAFU	2	2015-06-29 05:19
yafu 1.32	bsquared	YAFU	28	2012-07-20 16:17

2021-09-16, 13:41	#238
James Heinrich "James Heinrich" May 2004 ex-Northern Ontario E7E₁₆ Posts	If you think it's relevant, you might use the attachment feature of the forum to attach your .ini file to avoid any copy-paste-edit garbling.

2021-09-16, 16:48	#241
EdH "Ed Hall" Dec 2009 Adirondack Mtns 3×19×79 Posts	Just an additional note that the other Xeon acted the same. I forgot to include it in the last post.