![]() |
![]() |
#1 |
Basketry That Evening!
"Bunslow the Bold"
Jun 2011
40<A<43 -89<O<-88
3·29·83 Posts |
![]()
So, as a byproduct of other work that's going on, YAFU has the potential to implement a fully featured test sieving mechanism. So I'm curious: those who would use it, what features would you most desire?
Should it be an option to nfs(), e.g. `"nfs(num)" -nt file1,file2,file3`? Would you prefer it to be its own function, e.g. `"trialsieve(num, file1, file2, ...)"`? (In each case, the arguments would be names of job files with different poly/params.) What options should there be? Some things I can think of that would need configurability are qrange, qstart, and maybe even give a list of qstarts to properly trial sieve the whole sieving range. Another option may be to trial sieve the polys in parallel, though that wouldn't be enabled by default due to potential gotchas. (Edit: I mean one jobfile per thread.) Last fiddled with by Dubslow on 2012-12-31 at 09:52 |
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Two sieving questions | The Carnivore | Twin Prime Search | 13 | 2019-07-06 03:11 |
Test Sieving Questions | nstaab1 | Lounge | 15 | 2013-03-06 13:48 |
Automated PRP using LLRNet | axn | Sierpinski/Riesel Base 5 | 73 | 2008-11-26 03:46 |
Automated PRP discussions | ltd | Sierpinski/Riesel Base 5 | 20 | 2006-09-02 22:19 |
Automated P-1 thoughts. | nucleon | Marin's Mersenne-aries | 3 | 2004-03-25 02:45 |