With the newest version of Yafu, I am finding that the optimum crossover is likely > 100 and that's on a 2-year-old I7 running at 2.6 Ghz. (I don't overclock.) For now, I'm using 100 but I'll do some testing later on to figure out what is best. 94 or 95 is definitely not optimum. Yafu QS is FAST running on multiple cores!

But...if one does what LaurV suggested, i.e.:
[quote]
...use "yafu -tune()", as a separate command, to set the crossover to some optimum value depending on your machine, and delete the xover line (comment it out) in the ini. You will get better performance, as the optimum crossover depends on the machine.
[/quote]

Then you don't need to know what the optimum crossover is. Yafu will figure it out based on your machine.

It's not easy for me to test that one way or another. I may just try it for a while and see if I get a performance similar to or hopefully better than having the value hard-coded.

[QUOTE=henryzz;354759]I am surprised that is so high. Maybe I need to check again with a later version of yafu. Once upon a time the optimal value was around 95 with 64-bit everything. Yafu will have improved since then I suppose.[/QUOTE]

Meant to say - the tune info is with Yafu v.1.34.5

[QUOTE=Antonio;354831]Meant to say - the tune info is with Yafu v.1.34.5[/QUOTE]
Last time I tuned was probably with 1.10 or something rediculous

Aliqueit Crash with "WARNING: bad factor found: 5"
 

Darn my luck -- I get a downdriver run and Aliqueit crashes!

I have tried swapping prefer_yafu between true and false and all that does is add in a "running qs (msieve)..." line.

From my aliqueit.log:
[code]
...
[Jan 19 2014, 10:46:39] *** Starting 915684:1511 = 285784543673563430739334 (24 digits)
[Jan 19 2014, 10:46:39] *** prp1 = 2
[Jan 19 2014, 10:46:39] *** prp1 = 7
[Jan 19 2014, 10:46:39] *** prp2 = 13
[Jan 19 2014, 10:46:39] *** prp2 = 17
[Jan 19 2014, 10:46:39] *** prp3 = 223
[Jan 19 2014, 10:46:39] *** prp4 = 5237

[Jan 19 2014, 10:46:39] Cofactor 79091714583611 (14 digits)

[Jan 19 2014, 10:46:39] c14: running rho...
[Jan 19 2014, 10:46:39] *** c10 = 2435164709

[Jan 19 2014, 10:46:39] c10: running rho...

[Jan 19 2014, 10:46:39] c10: running qs (yafu)...
[Jan 19 2014, 10:46:39] WARNING: bad factor found: 5
01/19/14 10:46:39 v1.34.5 @ math34, starting smallmpqs on C10: 2435164709
01/19/14 10:46:39 v1.34.5 @ math34, prp1 = 5
01/19/14 10:46:39 v1.34.5 @ math34, prp10 = 2435164709
[Jan 19 2014, 10:46:39] *** c10 = 2435164709

[Jan 19 2014, 10:46:39] c10: running rho...
...
[/code]Similar with prefer_yafu=false:
[code]
...
[Jan 19 2014, 10:52:50] *** Starting 915684:1511 = 285784543673563430739334 (24 digits)
[Jan 19 2014, 10:52:50] *** prp1 = 2
[Jan 19 2014, 10:52:50] *** prp1 = 7
[Jan 19 2014, 10:52:50] *** prp2 = 13
[Jan 19 2014, 10:52:50] *** prp2 = 17
[Jan 19 2014, 10:52:50] *** prp3 = 223
[Jan 19 2014, 10:52:50] *** prp4 = 5237
[Jan 19 2014, 10:52:50] *** c10 = 2435164709

[Jan 19 2014, 10:52:50] c10: running rho...

[Jan 19 2014, 10:52:50] c10: running qs (msieve)...

[Jan 19 2014, 10:52:50] c10: running qs (yafu)...
[Jan 19 2014, 10:52:50] WARNING: bad factor found: 5
01/19/14 10:52:50 v1.34.5 @ math34, starting smallmpqs on C10: 2435164709
01/19/14 10:52:50 v1.34.5 @ math34, prp1 = 5
01/19/14 10:52:50 v1.34.5 @ math34, prp10 = 2435164709
[Jan 19 2014, 10:52:50] *** c10 = 2435164709

[Jan 19 2014, 10:52:50] c10: running rho...
...
[/code]c10 = 2435164709 = 21587 * 112807

But, I see it being called prp above. Any help?

BTW, all programs are up-to-date and this isn't one of my ancient machines::smile:
core 2 quad core 4G RAM

Thanks for any help...

Can you create the new line in the .elf manually, and let aliqueit just continue onto the next line?

[QUOTE=VBCurtis;364900]Can you create the new line in the .elf manually, and let aliqueit just continue onto the next line?[/QUOTE]
Actually, I fed Aliqueit one of the factors, via the -f option and it stepped to the next line and did the same thing. It kept doing it until I took the .elf to another machine, where it added some more lines. Interestingly, the second machine has displayed the identical behaviour in the past, but I just worked around it that time. When I moved back to the original machine, it added many lines and then did the same, again. I have kept a copy of the .elf at that point to experiment with, as desired.

Here's the aliqueit.log section for that run:
[code]
[Jan 19 2014, 16:23:52] *** Starting 915684:2394 = 486308988132605250820828474054756417783557491729493124060168984953778543236406694425640 (87 digits)
[Jan 19 2014, 16:23:52] *** prp1 = 2
[Jan 19 2014, 16:23:52] *** prp1 = 2
[Jan 19 2014, 16:23:52] *** prp1 = 2
[Jan 19 2014, 16:23:52] *** prp1 = 5

[Jan 19 2014, 16:23:52] Cofactor 12157724703315131270520711851368910444588937293237328101504224623844463580910167360641 (86 digits)

[Jan 19 2014, 16:23:52] c86: running rho...
[Jan 19 2014, 16:23:52] *** c10 = 3012104413

[Jan 19 2014, 16:23:52] c10: running rho...

[Jan 19 2014, 16:23:52] c10: running qs (yafu)...
[Jan 19 2014, 16:23:52] WARNING: bad factor found: 13
01/19/14 16:23:52 v1.34.5 @ math34, starting smallmpqs on C10: 3012104413
01/19/14 16:23:52 v1.34.5 @ math34, prp2 = 13
01/19/14 16:23:52 v1.34.5 @ math34, prp10 = 3012104413
[Jan 19 2014, 16:23:52] *** c10 = 3012104413

[Jan 19 2014, 16:23:52] c10: running rho...
[/code]I have also run mprime stress testing with no failures. And, after I have worked well past the area on another machine, it is now running well, further on.

I have discovered something interesting, though and will probably move this discussion to a YAFU thread (unless B[SUP]2[/SUP] pops in here):
[code]
01/19/14 16:25:24 v1.34.5 @ math34, System/Build Info:
Using GMP-ECM, Powered by GMP
detected Intel(R) Core(TM)2 Quad CPU Q9400 @ 2.66GHz
detected L1 = 32768 bytes, L2 = 3145728 bytes, CL = 64 bytes
measured cpu frequency ~= 2659.670720
using 20 random witnesses for Rabin-Miller PRP checks

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


>> siqs(3012104413)



***factors found***

P2 = 13
C10 = 3012104413
1
>>[/code]Unfortunately, this all seems familiar about YAFU having some kind of trouble at some digit value, but my memory is too poor to find that discussion and I thought it had been taken care of.

Thanks for the help...

I'm adding this as a separate post, so it isn't missed by someone:

Anyway, the reason why msieve didn't work when I tried prefer_yafu false is because I'm using an msieve binary with MPI and it returns the factors in .log.mpi00 instead of .log where Aliqueit searches. I can remedy that easily in Aliqueit, but that doesn't address the YAFU issue...

Edit: The above seems incorrect as in that I cannot make msieve (siqs) work at all in finding the factors for Aliqueit - another puzzle to frustrate me.:sad:

Edit2: I have the prefer_yafu = false version working now with a copy of msieve without MPI. I don't know how, but the msieve.log file was hidden along with a 1.6G msieve.dat file. They appeared when I commented out the delete msieve.log line in aliqueit.cc. The msieve.log file had all the previous runs in it. I deleted both and reinstated the original line in aliqueit.cc and msieve now works. prefer_yafu = true still does not.

It appears to be one of the upgrades that broke it. Upgrading other machines broke them, too:sad: I've posted in the YAFU thread and, if I get a chance, I'll try to see which upgrade broke it.

I'd be interested if anyone else has this trouble...

Here 1.34.3, with MPIR under Win64, it is working well. Didn't try other combinations. If it works, don't fix it!

[CODE]
01/20/14 09:49:47 v1.34.3 @ NB-12906, System/Build Info:
Using GMP-ECM 6.4.2, Powered by MPIR 2.6.0
detected Intel(R) Core(TM) i5-3340M CPU @ 2.70GHz
detected L1 = 32768 bytes, L2 = 3145728 bytes, CL = 64 bytes
measured cpu frequency ~= 2690.490420
using 20 random witnesses for Rabin-Miller PRP checks

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

>> siqs(3012104413)

***factors found***

P5 = 97577
P5 = 30869

ans = 1

>>[/CODE]

I've isolated it to YAFU. See [URL="http://www.mersenneforum.org/showpost.php?p=364946&postcount=255"]this post[/URL].

The current version (1.12 linux) is in need of updating. I've had to remove the b2scale portions from the source code and change the factorization.ath.cx reference to factordb.com to report factors.

Is no one else having these issues? Is anyone else using Aliqueit on linux?

I would prefer an "official" version with updates over my local modifications...