YAFU 2.0

[James Heinrich]

NFS screen output shows up ugly under Win10, see attached. Something about mangled CRLF I guess?

[Stargate38]

I've had that happen too. It must be a bug in YAFU, as it doesn't happen in other command line software.

[James Heinrich]

Would it be possible to have YAFU (optionally) output to factor.log a partial-progress report on ECM, either after every <1000> curves, or better would be if no output to factor.log has happened in the last <60> minutes. It would be useful (to me anyways) to both easily check progress on a remote machine and provide some fallback in the event of power failure or similar.

[BudgieJane]

Originally Posted by bsquared

The freq is unused, I think tune just assigns it the value '42' for now. Because, reasons.

According to Douglas Adams, 42 is the answer to the meaning of life, the universe, and everything. Maybe they are the reasons?

[James Heinrich]

Is there somewhere a complete-idiot's-guide (i.e. Windows user) to getting YAFU2 compiled and working on linux (CentOS 8 in my case) ?

[EdH]

Originally Posted by James Heinrich

Is there somewhere a complete-idiot's-guide (i.e. Windows user) to getting YAFU2 compiled and working on linux (CentOS 8 in my case) ?

Have you looked at my "How I install YAFU2 onto my Ubuntu Machines" to see if it might help? It does not go into the details of using all the options, but it may be a place to start.

[henryzz]

Originally Posted by James Heinrich

Is there somewhere a complete-idiot's-guide (i.e. Windows user) to getting YAFU2 compiled and working on linux (CentOS 8 in my case) ?

Written for an older version but https://mersenneforum.org/showthread.php?t=23087 should be useful. Any differences to this probably should be added (in an appendix if they don't affect Ubuntu).

[BudgieJane]

I just updated tune_info for yafu 2.07 in my yafu.ini file

tune_info=Intel(R) Core(TM) i7-4710MQ CPU @ 2.50GHz,WIN64,8.66985e-06,0.221065,19.753,0.0695336,96.607,42

and then ran yafu 2.07 on a small number. Imagine my surprise when this turned up on the screen:

fac: check tune params contained invalid parameter(s), ignoring tune info.
        qs_mult = 0.000000e+00
        qs_exp = 0.000000e+00
        qs_freq = 0.000000e+00
        nfs_mult = 0.000000e+00
        nfs_exp = 0.000000e+00
        nfs_freq = 0.000000e+00

This seems strange when yafu claims that the parameters that it itself wrote to my yafu.ini file not 15 minutes earlier are invalid.
What's occurring?

[EdH]

Originally Posted by henryzz

Written for an older version but https://mersenneforum.org/showthread.php?t=23087 should be useful. Any differences to this probably should be added (in an appendix if they don't affect Ubuntu).

I've done a separate one for YAFU2. See the previous post I got in just before yours, so you missed it. Thanks for the mention.

[EdH]

Originally Posted by BudgieJane

I just updated tune_info for yafu 2.07 in my yafu.ini file
. . .
and then ran yafu 2.07 on a small number. Imagine my surprise when this turned up on the screen:
. . .

[This seems strange when yafu claims that the parameters that it itself wrote to my yafu.ini file not 15 minutes earlier are invalid.
What's occurring?

Try another "git pull." I think the earlier one I was experiencing this with, was also 2.07, but it was an earlier commit. My latest pull has been working fine with its new tune_info.

[BudgieJane]

Originally Posted by EdH

Try another "git pull." I think the earlier one I was experiencing this with, was also 2.07, but it was an earlier commit. My latest pull has been working fine with its new tune_info.

Thanks for the hint. I downloaded the executable, then ran tune again. No change.