![]() |
|
|
#122 | |
|
"Mark"
Apr 2003
Between here and the
11100101011012 Posts |
Quote:
As for the second issue, the documentation isn't clear on what happens if you do a PRP test for a number that is trivially prime. I'll probably change the code to do as you suggest. |
|
|
|
|
|
|
#123 |
|
"Mark"
Apr 2003
Between here and the
3·2,447 Posts |
I found the first problem. It affects 64-bit Windows builds only when working with numbers between 32 and 64 bits in size. This bug does not affect Mac or Linux builds.
Last fiddled with by rogue on 2012-08-21 at 20:05 |
|
|
|
|
|
#125 |
|
Just call me Henry
"David"
Sep 2007
Liverpool (GMT/BST)
3·23·89 Posts |
If I am testing a file with the header:
ABC $a*2^$b-1 & $a*2^$b+1 & $a*2^$b+5 then if I find prime for all of these three forms then it outputs - Complete Set - in pfgw.out. Is there a way for getting it to stop testing after the first complete set of primes like there is for a single prime? Could this make it into the coming release? |
|
|
|
|
|
#126 | |
|
"Mark"
Apr 2003
Between here and the
3·2,447 Posts |
Quote:
The only alternative I can think of is to use a pfgw script. |
|
|
|
|
|
|
#127 |
|
Just call me Henry
"David"
Sep 2007
Liverpool (GMT/BST)
3×23×89 Posts |
|
|
|
|
|
|
#128 |
|
"Mark"
Apr 2003
Between here and the
3·2,447 Posts |
I have posted pfgw 3.6.6 over at sourceforge. Right now only the Windows build is available, but I hope to have the Mac and Linux builds available in the next day or two.
The only change is that pfgw 3.6.6 uses gwnum 27.8. This release of gwnum fixes an infinite loop that occurs with small AVX FFTs of the form k*b^n+c where abs(c) != 1. |
|
|
|
|
|
#129 |
|
Just call me Henry
"David"
Sep 2007
Liverpool (GMT/BST)
3×23×89 Posts |
I was just running tests to see how long each test would take on a number to determine the sieve depth. I ended up running a full 35 minute test to get a time. Is there a way to get iteration times in pfgw so I can extrapolate?
Another issue I can across is that I ended up doing quite of lot of tests to discover where the fft boundaries are. Is there an easier way pfgw can allow you to access this information? |
|
|
|
|
|
#130 | |
|
"Mark"
Apr 2003
Between here and the
3·2,447 Posts |
Quote:
pfgw does not have code to determine where the FFT boundaries are. I don't know how easy that would be to code. I might need some help from George (Prime95) for that. Often what I do is about 10% of the PRP test, then extrapolate from that. |
|
|
|
|
|
|
#131 | |
|
Just call me Henry
"David"
Sep 2007
Liverpool (GMT/BST)
3·23·89 Posts |
Quote:
|
|
|
|
|
|
|
#132 | |
|
"Mark"
Apr 2003
Between here and the
3×2,447 Posts |
Quote:
I agree that it would be better if PFGW could do that itself, but the challenge is the change in FFT boundaries. PFGW has no knowledge of that. |
|
|
|
|
![]() |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| A possible bug in LLR/PFGW while using GWNUM (no bug in P95) | Batalov | Software | 77 | 2015-04-14 09:01 |
| PFGW 3.2.0 has been Released | rogue | Software | 94 | 2010-09-14 21:39 |
| PFGW 3.2.3 has been Released | rogue | Software | 10 | 2009-10-28 07:07 |
| PFGW 3.2.1 has been released | rogue | Software | 5 | 2009-08-10 01:43 |
| PFGW 3.1.0 has been Released | rogue | Software | 25 | 2009-07-21 18:13 |