YAFU cli parameters

[VolMike]

I want to use YAFU 1.32-1 in such way:

1) First do some rho,pm1..,etc and ecm testing ( usual stage before QS/NFS).
2) After the 1 step if the result is less then 70 digits, do the QS stage, otherwise - no QS or NFS methods executes and factoriziation stops (no matter if the result is composite).

I was trying this parameters : -xover 70 -plan light -ggnfsT 0 but yafu still executed QS for number > 70 digits length. What parameters should i use to satisfy the second step of factorization?

[bsquared]

Originally Posted by VolMike

I want to use YAFU 1.32-1 in such way:

1) First do some rho,pm1..,etc and ecm testing ( usual stage before QS/NFS).
2) After the 1 step if the result is less then 70 digits, do the QS stage, otherwise - no QS or NFS methods executes and factoriziation stops (no matter if the result is composite).

I was trying this parameters : -xover 70 -plan light -ggnfsT 0 but yafu still executed QS for number > 70 digits length. What parameters should i use to satisfy the second step of factorization?

Interesting. Unfortunately I can't think of a way to get this done out of the box. The reason QS is executed in your example is that there is a built-in lower limit on nfs jobs of 85 digits. Anything less than this gets redirected to qs, even if you specify nfs() directly. Otherwise one would think your approach would have worked, but, in fact it would have just led to an infinite loop. The reason is that factor() expects sieve methods to always work, and if they don't find factors it will automatically recurse on any leftover composite.

In general, factor() tries really hard to find *all* of the factors, although there are a number of options that modify that behavior. Options that are associated with particular algorithms, like ggnfsT, were not necessarily designed to work well with factor(), with potential unintended consequences (like infinite loops).

The best I can suggest is to use "-pretest -ou composites.txt", which will test the input with trial, rho, p-1, and ecm, and then put any leftover composite in the file composites.txt. You can then (externally to yafu) sort and cut out any numbers you don't want to process further, and then re-submit the modified composites.txt file as a batchfile input to qs like so:

./yafu "siqs(@)" -batchfile composites.txt

[VolMike]

The best I can suggest is to use "-pretest -ou composites.txt", which will test the input with trial, rho, p-1, and ecm, and then put any leftover composite in the file composites.txt. You can then (externally to yafu) sort and cut out any numbers you don't want to process further, and then re-submit the modified composites.txt file as a batchfile input to qs like so:

./yafu "siqs(@)" -batchfile composites.txt

Interesting way! Thanks, i'll try this idea.

[deventonio]

First of all you must guarantees that YAFU 1.32.1 is 100% CLEAN, which means it does not contain any form of malware, including spyware, viruses.Please enable it or use sftp or scp.

[bsquared]

Originally Posted by deventonio

First of all you must guarantees that YAFU 1.32.1 is 100% CLEAN, which means it does not contain any form of malware, including spyware, viruses.Please enable it or use sftp or scp.

??

[pinhodecarlos]

It was his first post...

[Dubslow]

Originally Posted by deventonio

First of all you must guarantees that YAFU 1.32.1 is 100% CLEAN, which means it does not contain any form of malware, including spyware, viruses.

You can compile it yourself

[VolMike]

Originally Posted by bsquared

The best I can suggest is to use "-pretest -ou composites.txt", which will test the input with trial, rho, p-1, and ecm, and then put any leftover composite in the file composites.txt.

It seems that "-ou" flag only returnes an input number if yafu doesn't find any factor until it's stopped (not the leftover composites). F.e factor(
3757160792909754673945392226295475594863*6918082374901313855125397665325977135579*5
) -pretest -ou composites.txt get nothing in composites.txt.

[Kosmaj]

IMO, leftover composites go to the file specified by "-of compos.out".
Usually, I use all 3: -op, -of, -ou.