[QUOTE=bsquared;577458]No, those symbols should be in libmsieve, the linker just can't find the library to link them in. I don't know anything else to try. You just need to make sure that a path to the location where libmsieve.a exists is in the LIBS variable of the makefile. You could try an absolute path.[/QUOTE]

Oh, and you also need a -lmsieve in there somewhere too.:blush:

LIBS += -L../msieve -lmsieve

Thank you.... !!! :D


That was it. Why does it seem to work for almost everyone without that but not for me? Or did I delete it at some point?

[QUOTE=bur;577548]Thank you.... !!! :D


That was it. Why does it seem to work for almost everyone without that but not for me? Or did I delete it at some point?[/QUOTE]

It was deleted back when I told you that you could simplify the ifeq ($(NFS),1) block back in post 54. you can see it there at the end of the original NFS block in that post. Just been overlooking it since then. :doh!:

I have gotten around to starting a new "How I. . ." thread specifically for YAFU2. It's based on Makefile modification rather than command line massaging, and it's meant only as a starting point to getting it up and running. Sorry, it's a little late. Any comments are quite welcome.

As a general question, how often do you guys build a new version of yafu or cado? Should I just check the repository for the changelog?

Well, I've just got it to work, which is quite something for me!

I persuaded it to do
[CODE]nfs(29^165 - 23^165)[/CODE]
which has 240 decimal digits, and it only took a few hours to come up with
[CODE]***factors found***

P1 = 2
P1 = 3
P1 = 3
P1 = 7
P2 = 31
P2 = 31
P2 = 67
P2 = 97
P3 = 199
P3 = 331
P4 = 2441
P4 = 3301
P37 = 3126480058316999071399277955199677901
C125 = 12724988150963378912700523668030562454652746526621625001448059255431251645943099394682519998040029913891319413189363203274486
P25 = 5021659044902186258192281
P18 = 102397541093560351
P39 = 965650242131801601223534344035881987891

ans = 0[/CODE]
which I am quite satisfied with as I already had the factors for the C125 cofactor.

Things missing in output from Version 2.0
 

Following on from yesterday's post, I have now started using yafu2.0 in my application. What gets run is the following (example):
[CODE]..\..\Maths\yafu\Versions\yafu-2.0\yafu-x64 factor(1093398016684859039437357097655002878473578346491832162155479546307786424669365857546034634142930096044072838434811201) -forceDLP -v -v -v -noecm -silent -R -logfile io\log12.txt -of io\out12.txt[/CODE]

The first thing I noticed is the version number and the host name do not appear in the log file, whereas they did in previous versions. These may be important for figuring out which version was used when comparing runs between future versions.

The second thing I noticed is that whereas the -logfile was created, the -of (output file) was not. This is the way I pass the output from yafu to my application, as it is much easier to parse this than to try to parse the logfile.

[QUOTE=BudgieJane;577700]I noticed is the version number does not appear in the log file, whereas it did in previous versions. This may be important for figuring out which version was used when comparing runs between future versions.
[/QUOTE]
+1. Needed. We did such comparisons many times in the past.

[QUOTE=LaurV;577701]+1. Needed. We did such comparisons many times in the past.[/QUOTE]

I guess I didn't realize that was useful to folks, sorry about that. I removed it, well, actually because the code reorg made it harder to implement, but I told myself it was because it wasn't useful. I will look into putting it back.

As for the -of output, can confirm that it isn't working. That was not tested at all and apparently I broke it somehow. I'll get it fixed.

Also, Jane, this one had a small-ish factor (found by ecm):

[CODE]
found factor 24616664227663950740856773434561 in stage 2 in thread 9, vec position 4, with sigma = 3667020861

found factor 24616664227663950740856773434561 in stage 2 in thread 35, vec position 7, with sigma = 544625459

found factor 24616664227663950740856773434561 in stage 2 in thread 40, vec position 5, with sigma = 3261427245
ecm: 768/912 curves on C118 @ B1=1000000, B2=100*B1
ecm: process took 21.6734 seconds.

ecm: found prp32 factor = 24616664227663950740856773434561

ecm: found prp86 (co)factor = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
Total factoring time = 40.2258 seconds


***factors found***

PRP32 = 24616664227663950740856773434561
PRP86 = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
[/CODE]

I can't remember why I added the -noecm keyword in there, although I may have thought the small amount of ecm processing slowed the average factoring time down a bit. Obviously it didn't. I shall remove it.

BTW the file docfile.txt claims to be for Version 1.35-beta. Should this be changed to 2.0?

[QUOTE=bsquared;577705]I guess I didn't realize that was useful to folks, sorry about that. I removed it, well, actually because the code reorg made it harder to implement, but I told myself it was because it wasn't useful. I will look into putting it back.[/QUOTE]

It was appearing on every line of the logfile in the old versions. In my opinion it is only needed in there once, if that makes things any easier, although you might want to get LaurV's opinion on that, too.

[QUOTE=bsquared;577705]As for the -of output, can confirm that it isn't working. That was not tested at all and apparently I broke it somehow. I'll get it fixed.

Also, Jane, this one had a small-ish factor (found by ecm):

[CODE]
found factor 24616664227663950740856773434561 in stage 2 in thread 9, vec position 4, with sigma = 3667020861

found factor 24616664227663950740856773434561 in stage 2 in thread 35, vec position 7, with sigma = 544625459

found factor 24616664227663950740856773434561 in stage 2 in thread 40, vec position 5, with sigma = 3261427245
ecm: 768/912 curves on C118 @ B1=1000000, B2=100*B1
ecm: process took 21.6734 seconds.

ecm: found prp32 factor = 24616664227663950740856773434561

ecm: found prp86 (co)factor = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
Total factoring time = 40.2258 seconds


***factors found***

PRP32 = 24616664227663950740856773434561
PRP86 = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
[/CODE][/QUOTE]

I got the same answer (eventually!):
[CODE]05/05/21 13:18:03, prp86 = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
05/05/21 13:18:03, prp32 = 24616664227663950740856773434561
05/05/21 13:18:03, NFS elapsed time = 8640.5802 seconds.[/CODE]

There is one thing I have forgotten to say on all these emails, and that is THANK YOU for all the work you have put into updating yafu so that retired old codgers like me can keep my brain active in my dotage.

[QUOTE=BudgieJane;577711]I can't remember why I added the -noecm keyword in there, although I may have thought the small amount of ecm processing slowed the average factoring time down a bit. Obviously it didn't. I shall remove it.

[/QUOTE]

It depends on the inputs, of course. If you are attempting these inputs for the first time then some ecm will help a lot. If they have already been ecm'ed, by you or someone else, then more ecm might not help much. -plan custom and -pretest_ratio X can help fine tune how much time you spend on ecm.

[QUOTE=BudgieJane;577711]

BTW the file docfile.txt claims to be for Version 1.35-beta. Should this be changed to 2.0?

[/QUOTE]

Yes. Every time I contemplate updating that file I suddenly find myself doing something else. Maybe this isn't a coincidence (documentation is a chore).

[QUOTE=BudgieJane;577711]
It was appearing on every line of the logfile in the old versions. In my opinion it is only needed in there once, if that makes things any easier, although you might want to get LaurV's opinion on that, too.

[/QUOTE]

If you use session.log (active by default), then the version and build info appears in there. Date stamps can be correlated to factor.log output, should that be needed. Is that enough? Feedback welcome.

[CODE]
05/05/21 09:31:52, =====================================
05/05/21 09:31:52, System/Build Info:
05/05/21 09:31:52, YAFU Version 2.0
05/05/21 09:31:52, Built with Intel Compiler 1910
05/05/21 09:31:52, Using GMP-ECM 7.0.4, Powered by GMP 6.2.0
05/05/21 09:31:52, detected Intel(R) Xeon(R) Gold 6254 CPU @ 3.10GHz
detected L1 = 32768 bytes, L2 = 25952256 bytes, CL = 64 bytes
05/05/21 09:31:52, using 1 random witness for Rabin-Miller PRP checks
05/05/21 09:31:52, Cached 664579 primes: max prime is 9999991

05/05/21 09:31:52, Random seed: 11617470479886605489
05/05/21 09:31:52, Processing: factor(rsa(300))
05/05/21 09:32:19, Result : 1
[/CODE]

[QUOTE=BudgieJane;577711]
I got the same answer (eventually!):
[CODE]05/05/21 13:18:03, prp86 = 44416985444197989346245849525036029769673491288448206702392870361399028860459766362241
05/05/21 13:18:03, prp32 = 24616664227663950740856773434561
05/05/21 13:18:03, NFS elapsed time = 8640.5802 seconds.[/CODE]
[/QUOTE]

I can occasionally run on some really nice hardware so don't feel bad... 40 sec is not typical, even if some ecm had been done (I was running 768 curves in parallel)

[QUOTE=BudgieJane;577711]
There is one thing I have forgotten to say on all these emails, and that is THANK YOU for all the work you have put into updating yafu so that retired old codgers like me can keep my brain active in my dotage.[/QUOTE]

You're welcome, glad it is finding some use and thank you for all the feedback.