mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   Software (https://www.mersenneforum.org/forumdisplay.php?f=10)
-   -   LLR Version 3.8.15 released (https://www.mersenneforum.org/showthread.php?t=20217)

Jean Penné 2015-05-06 19:57

Mac Intel applications are available.
 
Hi,

Thanks to Iain Bethune, Mac Intel 32bit and 64bit applications are now available.
Regards,
Jean

Jean Penné 2015-05-07 19:58

Upgrading the version display
 
Hi,

At the request of Iain and PrimeGrid project, I upgraded the -v feature on current LLR Version ; now, ./llr -v or cllr -v give this output :

LLR Program - Version 3.8.15, using Gwnum Library Version 28.7

I uploaded the updated source, Win32 console, Linux 32bit and 64bit applications accordingly.
Mac Intel , and perhaps the Win64 console application, need to be rebuilt ; Windows GUI applications are not concerned, and so, not modified.

Regards,
Jean

Jean Penné 2015-05-09 07:43

[QUOTE=Jean Penné;401932]Hi,

At the request of Iain and PrimeGrid project, I upgraded the -v feature on current LLR Version ; now, ./llr -v or cllr -v give this output :

LLR Program - Version 3.8.15, using Gwnum Library Version 28.7

I uploaded the updated source, Win32 console, Linux 32bit and 64bit applications accordingly.
Mac Intel , and perhaps the Win64 console application, need to be rebuilt ; Windows GUI applications are not concerned, and so, not modified.

Regards,
Jean[/QUOTE]

Thanks to Iain, Mac Intel applications are now updated on this release.
Regards,
Jean

Jean Penné 2015-05-09 20:56

[QUOTE=Jean Penné;402021]Thanks to Iain, Mac Intel applications are now updated on this release.
Regards,
Jean[/QUOTE]

Thank to Rebirther, the Win64 Console and GUI applications are now also updated in this release.
Regards,
Jean

stream 2015-05-11 19:53

Jean, thank you for update. Unfortunately, I afraid that we're moving in wrong direction. The change which you've suggested and implemented may work for PrimeGrid, but I'd rather call it not a solution, but a workaround.

I'll post a summary of the problem once again here. I would be very appreciated to hear opinions of other developers, how this situation is handled in their programs.

The problem which affected PrimeGrid seems to be in LLR for ages. It's in the logic how LLR behaves with ErrorCheck=1 option (so why PG does not using ErrorCheck). First time it was described in [URL="http://www.primegrid.com/forum_thread.php?id=6269&nowrap=true#85444"]this post[/URL]. The scenario is following.[INDENT] 1) LLR have following piece of code:[/INDENT][code]if (error_count > MAX_ERROR_COUNT) {\
OutputBoth (ERRMSG9);\
care = TRUE;\
}\[/code][INDENT]where MAX_ERROR_COUNT=5.[/INDENT][INDENT] 2) When a "repeatable" roundoff error (>0.4) occurs (i.e. this is not a hardware fault, but an unlucky FFT size), after fixing the error itself with few "careful" iterations, an error_count is incremented, and nothing else is done.
[/INDENT][INDENT] 3) It's possible that very long (SoB) unlucky candidate will generate more then 5 RoundOff errors. According to the condition above, a "care" flag is set, and, as far as I understand, ALL operations from now on will be done using "careful" functions. This leads to deadly effects - according to the original post, "The result was that LLR was going to take 11.3 days instead of 2.7 days.". This is completely unacceptable for PrimeGrid due to return timeouts, possible complains about credits, etc.
[/INDENT]This leads to a question: how this situation (multiple "soft" RoundOffs per candidate) are handled in other programs? I see two trivial solutions which will be compatible with PG:
[LIST=1][*]No need to handle this case at all. The code above must be completely removed. Why this magic number of 5 errors appeared at all? Since this is not a hardware problem, let's continue to crunch and recover (if necessary) in usual way.[*]Restart with FFT_Increment. Details of implementation could be discussed (should it restart on first error? 2? 3? 5?). This is good because it'll be no future errors and restarts, and acceptable for PG because FFT_Increment is really not so time-consuming (from original post - "It took an hour or two longer than with the original FFT size" - with 2.7 days total).[/LIST]Any comments are appreciated.

Roman

paulunderwood 2015-05-17 03:36

LLR timings / FFT sizes for different k
 
[CODE]Starting Lucas Lehmer Riesel prime test of 733*2^1001099-1
Using FMA3 FFT length 64K, Pass1=256, Pass2=256
733*2^1001099-1 is not prime. LLR Res64: 394E30CF7BB572C3 Time : 167.814 sec.
Starting Lucas Lehmer Riesel prime test of 9959*2^1000040-1
Using FMA3 FFT length 80K, Pass1=320, Pass2=256
9959*2^1000040-1 is not prime. LLR Res64: 0AF38FB979C9314F Time : 214.790 sec.
[/CODE]

Are smaller FFT sizes chosen for small k?

Batalov 2015-05-17 03:39

They always were.

paulunderwood 2015-05-17 03:45

Thanks for the info :smile:

rogue 2015-05-25 00:40

A change was made to LLR 3.8.15 that does not work with PRPNet. I'm testing a change with the client to address the problem. Please do not use LLR 3.8.15 with PRPNet until PRPnet is updated.

pepi37 2015-06-03 19:52

Just cosmetic change: can somebody add to windows version that prime is highlighted ( like in linux version) in next release.

Jean Penné 2015-06-04 06:28

Special character(s)?
 
[QUOTE=pepi37;403463]Just cosmetic change: can somebody add to windows version that prime is highlighted ( like in linux version) in next release.[/QUOTE]

I will add this in the next release, but need help to know what special character(s) most be sent to the console,
the magic : OutputStr("\033[7m"); works on Linux, but does not work on Windows...

Regards,
Jean


All times are UTC. The time now is 06:14.

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