Just something that I've been thinking about - would it be possible to add a driver recognition system to aliqueit, and let it alert you when you acquire or escape a driver (including the downdriver)? I presume it wouldn't be much use below, say, 80 digits, but above, it could be good for detecting records - they don't always get spotted...

[QUOTE=10metreh;191365]Just something that I've been thinking about - would it be possible to add a driver recognition system to aliqueit, and let it alert you when you acquire or escape a driver (including the downdriver)? I presume it wouldn't be much use below, say, 80 digits, but above, it could be good for detecting records - they don't always get spotted...[/QUOTE]

Certainly possible, but I don't think I personally will be doing it. Time has become a somewhat limited resource lately. Perhaps it would be better to write a simple separate app that goes through an elf file and looks for records? If someone else wrote the code for it and wanted it merged into aliqueit and accessible via a cmdline switch that'd be fine too. Whatever makes you happy is ok with me as long as I don't have to be the clown. :smile:

bsquared:
My mistake: the CF was 103 not 85, sorry.
I have a very very few things that i wrote to try understand the qs and try optimize this process.
Can I send one Pm for you, with my "work", for your analysis?
P.S: that's one very very iniiant analisys.
Again, thank you for your attention.

[quote=zarabatana;191379]Can I send one Pm for you, with my "work", for your analysis?
[/quote]

Yes, go ahead.

(not sure if you were waiting for a response here...)

Yes, I was.
I sent now 2 Pm's for you.
Thank you very much for your attention and patience, and the time and patience of 10metreh and mklasson too.

Is there a way to force aliqueit.exe to continue running a sequence even if it's apparently merged with an earlier sequence? Am playing with some miscellaneous numbers, and every two steps I need to start a new aliquiet <num> command to continue the sequence. The earlier sequence isn't "known", so it's a bit frustrating.


Edit: Looking in the aliqueit.ini file, setting detect_merge = false looks to be the trick!

For anything with ecm, one example does not tell you much. ecm is a gamble. More ecm will be faster for some numbers and slower for other numbers.

Since aliqueit has ecm, it will sometimes be faster and sometime slower. What matters is what happens overall which is harder to measure.

[QUOTE=Greebley;191522]For anything with ecm, one example does not tell you much. ecm is a gamble. More ecm will be faster for some numbers and slower for other numbers.

Since aliqueit has ecm, it will sometimes be faster and sometime slower. What matters is what happens overall which is harder to measure.[/QUOTE]

Agreed. IMHO, the only method to compare the speed of ECM is to look how much time it takes per ECM-curve.

[quote=smh;179632]IIRC 0.7 does to much sieving on smaller numbers.

0.5 is what I'm using most of the time (although these days I use the minrels file).[/quote]

I have found a single constant doesn't work that well. I see a reference to minrels.txt file in factmsieve.pl which is what you are talking about? If this is better than a single constant, does anyone have such a file with reasonable values set? I think it would be faster if I could use a smaller falue for the low end and bigger for the high end.

im having trouble with this at the moment.i keep getting this error when it goes to use yafu.
[QUOTE]Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\X>"C:\Documents and Settings\XXXXXXX\aliqueit108\aliqueit108\aliqueit_win32.ex
e" 6669696
WARNING: couldn't open config file.
verifying index 57... Everything looks OK!
Precalcing primes for trial factoring...
seq = 6669696
index = 58
value = 5817360552461555640 (19 digits)
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
'yafu' is not recognized as an internal or external command,
operable program or batch file.
WARNING: couldn't find factor in factor.log
WARNING: couldn't find factor in msieve.log
WARNING: qs failed to find a factor. This really shouldn't happen.
I'll cheerfully loop and try again though...
c17: running qs (^C
C:\Documents and Settings\X> [/QUOTE]

whats my problem??

[quote=Dougal;199946]im having trouble with this at the moment.i keep getting this error when it goes to use yafu.


whats my problem??[/quote]
My guess: It's looking in C:\Documents and Settings\X\ for files that are in C:\Documents and Settings\XXXXXXX\aliqueit108\aliqueit108\ Run it from the aliqueit108 directory (or in a way that makes it look there, like with a shortcut with the proper settings, or adding aliqueit's directory to the PATH variable) and it should work right.