LLR Version 3.8.9 released - Page 2

Cruelty · 2012-09-22, 13:30

Thanks for the hint. Below line will launch an instance of cllr64.exe to run on CPU6 (actually 4th physical core of 3770K) - it took me a while to understand the "affinity mask"

Code:

start "cllr3" /affinity 40 cllr64.exe

Now how to make cllr64.exe to display progress in CMD window?
Fiddling with llr.ini and setting Verbose=1 doesn't help, window remains blank...

rogue · 2012-09-22, 16:06

Quote:

Originally Posted by Cruelty

Thanks for the hint. Below line will launch an instance of cllr64.exe to run on CPU6 (actually 4th physical core of 3770K) - it took me a while to understand the "affinity mask"

Code:

start "cllr3" /affinity 40 cllr64.exe

Now how to make cllr64.exe to display progress in CMD window?
Fiddling with llr.ini and setting Verbose=1 doesn't help, window remains blank...

Is there a command line option for cllr64?

Cruelty · 2012-09-22, 16:58

Quote:

Originally Posted by rogue

Is there a command line option for cllr64?

Code:

-d      Print detailed information to stdout.

One observation though: base=2 tests every 10k iterations are presented in a separate line on the screen, whereas base=113 status is updated in the same line...

rogue · 2012-09-22, 17:21

Probably due to the use of \n instead of \r in the code somewhere.

WraithX · 2012-09-22, 20:23

Quote:

Originally Posted by rogue

Probably due to the use of \n instead of \r in the code somewhere.

I don't think so. I think it is due to the fact that "iteration" is a much longer word than "bit". This causes the length of the info line to go over 80 characters and wrap around to the next line. Then after the \r is printed, it returns to the beginning of that next line and then starts printing the new line of info there.

The user can perform a work-around to get the desired behavior. On the top of the command window, right-click on the title bar (in the image, next to where it says "cllr3") and then select properties. Then select the Layout tab and increase the width to 100. (90 might work, but 100 definitely will) And in this wider window it should only print on one line. Let us know if this works for you.

To fix it from a developers perspective, the word iteration should be changed to bit, as it is in the cllrX program.

Cruelty · 2012-09-23, 07:01

Quote:

Originally Posted by WraithX

The user can perform a work-around to get the desired behavior. On the top of the command window, right-click on the title bar (in the image, next to where it says "cllr3") and then select properties. Then select the Layout tab and increase the width to 100. (90 might work, but 100 definitely will) And in this wider window it should only print on one line. Let us know if this works for you.

Thanks! It worked for me

ATH · 2013-02-17, 08:32

I tried to factor (2⁸¹⁹¹+1)/3, but I guess the exponent is too low? It just says "1 candidates factored, 0 factors found, 1 remaining" in the lresults.txt without doing anything.

pinhodecarlos · 2013-02-22, 14:52

How to resume work with llr64 console version on windows? What's the flag?

Edit: found it, -d.

ATH · 2013-02-28, 13:12

I know the "Vrba-Reix algorithm" for Wagstaff numbers are not fully proven, it is only a prp test. But when it says "not prime" then the number is composite with 100% certainty right? No need to run a strong fermat PRP test as well?

Edit: Nevermind. I didn't read the readme.txt properly, it gave me the answer:

Quote:

Both tests are known as a necessary condition for primality.

pinhodecarlos · 2013-03-11, 05:11

Is there a LLR Version 3.8.9 for MS Windows 64bit, GUI version?

pepi37 · 2013-03-13, 10:29

Quote:

Originally Posted by pinhodecarlos

Is there a LLR Version 3.8.9 for MS Windows 64bit, GUI version?

No, there is not and not will be that version. I asked author about 15 days ago, and got negative respond :(

2012-09-22, 13:30	#12
Cruelty May 2005 3134₈ Posts	Thanks for the hint. Below line will launch an instance of cllr64.exe to run on CPU6 (actually 4th physical core of 3770K) - it took me a while to understand the "affinity mask" Code: start "cllr3" /affinity 40 cllr64.exe Now how to make cllr64.exe to display progress in CMD window? Fiddling with llr.ini and setting Verbose=1 doesn't help, window remains blank...

2013-02-22, 14:52	#19
pinhodecarlos "Carlos Pinho" Oct 2011 Milton Keynes, UK 2×5×11×47 Posts	How to resume work with llr64 console version on windows? What's the flag? Edit: found it, -d. Last fiddled with by pinhodecarlos on 2013-02-22 at 14:54

2013-03-11, 05:11	#21
pinhodecarlos "Carlos Pinho" Oct 2011 Milton Keynes, UK 2·5·11·47 Posts	LLR Version 3.8.9 for MS Windows 64bit, GUI Is there a LLR Version 3.8.9 for MS Windows 64bit, GUI version?

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
LLR Version 3.8.20 released	Jean Penné	Software	30	2018-08-13 20:00
LLR Version 3.8.19 released	Jean Penné	Software	11	2017-02-23 08:52
LLR Version 3.8.15 released	Jean Penné	Software	28	2015-08-04 04:51
LLR Version 3.8.11 released	Jean Penné	Software	37	2014-01-29 16:32
llr 3.8.2 released as dev-version	opyrt	Prime Sierpinski Project	11	2010-11-18 18:24

2012-09-22, 17:21	#15
rogue "Mark" Apr 2003 Between here and the 3×2,447 Posts	Probably due to the use of \n instead of \r in the code somewhere.

2013-02-17, 08:32	#18
ATH Einyen Dec 2003 Denmark 2²×863 Posts	I tried to factor (2⁸¹⁹¹+1)/3, but I guess the exponent is too low? It just says "1 candidates factored, 0 factors found, 1 remaining" in the lresults.txt without doing anything.