[QUOTE=richs;617720]I sieved an Aliquot C141 using Yafu 2.0 and when the filtering ran, every relation was an error -11. Looking at the .fb file below, somehow Yafu did not include skew, rlim, frmax, famax, srlpmax, or salpmax.

[CODE]N 379940961516713825613865981760557035526784109230555165792877792447392213895676955608876175676740458184733360391979563490370537264576678836483
A0 17921599049871804734714330370707400
A1 884689986849071910726068107020
A2 1004298442072520798460436
A3 -54583391456339434
A4 -93062625051
A5 9180
R0 -2105596592265349121584460471
R1 1152139905935473[/CODE]


I got it to work by adding skew and the other parameters to the .fb file and running Yafu 1. I'm not sure if this was my error or if Yafu 2.0 did not include the parameters for some odd reason.[/QUOTE]


None of those parameters are needed for filtering, which is the only place .fb files are used. The .job file is where the ggnfs equivalent to those parameters are filled in, for sieving. I don't know why or how filling those parameters in here would cause it to work, or not, for either version. Usually when tons of -11's happen it's because a previous job didn't get cleared out somehow (power loss, job killed, etc.).

I can't factor 27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093
It freezes on commencing Lanczos iteration (8 threads)
memory use: 71.9 MB
with no cpu usage.
yafu "factor(27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093)" -p -threads 8

also it outputs
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.

[QUOTE=kotenok2000;624508]I can't [c]factor(27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093)[/c][/QUOTE][code]factor(27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093)

fac: factoring 27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093
fac: using pretesting plan: deep
fac: using specified qs/gnfs crossover of 100 digits
fac: using specified qs/snfs crossover of 100 digits
div: primes less than 10000
fmt: 1000000 iterations
rho: x^2 + 3, starting 1000 iterations on C101
rho: x^2 + 2, starting 1000 iterations on C101
rho: x^2 + 1, starting 1000 iterations on C101
nfs: searching for brent special forms...
nfs: searching for homogeneous cunningham special forms...
nfs: searching for XYYXF special forms...
nfs: searching for direct special forms...
nfs: snfs form detection took 0.055005 seconds
nfs: couldn't find special form
pm1: starting B1 = 150K, B2 = gmp-ecm default on C101
ecm: 128/32 curves on C101 @ B1=2000, B2=100*B1
ecm: process took 0.0630 seconds.
ecm: 128/80 curves on C101 @ B1=11000, B2=100*B1
ecm: process took 0.1130 seconds.
ecm: 256/224 curves on C101 @ B1=50000, B2=100*B1
ecm: process took 0.8514 seconds.
pm1: starting B1 = 3750K, B2 = gmp-ecm default on C101
ecm: 512/432 curves on C101 @ B1=250000, B2=100*B1
ecm: process took 7.3860 seconds.
pm1: starting B1 = 15M, B2 = gmp-ecm default on C101
ecm: 640/576 curves on C101 @ B1=1000000, B2=100*B1
ecm: process took 34.6520 seconds.
nfs: commencing nfs on c101: 27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093
nfs: searching for brent special forms...
nfs: searching for homogeneous cunningham special forms...
nfs: searching for XYYXF special forms...
nfs: searching for direct special forms...
nfs: snfs form detection took 0.079990 seconds
nfs: couldn't find special form
....
nfs: commencing msieve filtering
27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093
checking relations array at location 1
checking relations array at location 1
checking relations array at location 1
nfs: commencing msieve linear algebra
linear algebra completed 178084 of 179443 dimensions (99.2%, ETA 0h 0m)
nfs: commencing msieve sqrt
NFS elapsed time = 1844.8132 seconds.
Total factoring time = 1895.3412 seconds


***factors found***

P55 = 4009233200275881669007420627248030065788133608728404689
P46 = 6905885536470833185864058916647404865761283437

ans = 1[/code]

[QUOTE=kotenok2000;624508]I can't factor 27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093
It freezes on commencing Lanczos iteration (8 threads)
memory use: 71.9 MB
with no cpu usage.
yafu "factor(27687305570123882468203735526899284256078398738059989078472112075185421896509959250815385106168836093)" -p -threads 8

also it outputs
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.
line 225 - Failed to obtain a task from the jobs queue.
line 274 - Warning an error has occurred when trying to obtain a worker task.
line 275 - The worker thread has exited.[/QUOTE]

That error comes from inside the msieve library, and I haven't tracked down why it happens or how to fix it yet. Fortunately if you restart the job with the existing data set it should work.

from when did this msieve library error begin to appear and from what commit should i download yafu-x64.exe?

[QUOTE=bsquared;624511]That error comes from inside the msieve library, and I haven't tracked down why it happens or how to fix it yet. Fortunately if you restart the job with the existing data set it should work.[/QUOTE]

I've also been getting a similar error when I attempt to use 12 threads on YAFU 2.10, win 11, i7-12700k. It will either give the "workers failing to obtain tasks" messages or just silently hang at 0% cpu usage indefinitely. Retrying the job with 12 threads gives the same error, but restarting and only using 1 thread has successfully finished the job. For reference I was factoring C122 10090384354409393447889290770153099989080270065910033870159468230862477669938715326805661791618012360797542282091005502603

I'd attempt to see if 2.9 circumvents this problem but I'm not sure where to find older yafu binaries.

You can download them from github history.
[URL="https://github.com/bbuhrow/yafu/commits/master/bin/x64/Release"]https://github.com/bbuhrow/yafu/commits/master/bin/x64/Release[/URL]
Looks like yafu-x64 from commit aec7526 works.

[QUOTE=kotenok2000;624767]You can download them from github history.
[URL="https://github.com/bbuhrow/yafu/commits/master/bin/x64/Release"]https://github.com/bbuhrow/yafu/commits/master/bin/x64/Release[/URL]
Looks like yafu-x64 from commit aec7526 works.[/QUOTE]
Replacing my yafu-x64 executable in the directory with that one (after removing the cado related ini args) got me up and running! My only remaining yafu trouble is that I wish there was a way to estimate gnfs time ahead of actually running it.

Maybe we can build a table that matches composite length to runtime?

[QUOTE=kotenok2000;628089]Maybe we can build a table that matches composite length to runtime?[/QUOTE]Not sure if this is what you mean, but I this is the SIQS runtime formula I got by graphing many test results on my i7-3930K into Excel:
[c]8E-06 * pow(e, bits * 0.0579)[/c]
where [url=https://en.wikipedia.org/wiki/E_(mathematical_constant)]e[/url] = 2.718... and [c]bits[/c] is log2([c]composite[/c])

I was running a job for Studio Kamada yesterday with v2.09. A 137-digit composite. It got to a point where msieve filtering was to start, according to the last entry in the log file. What I saw was thousands of errors on a rapidly scrolling screen. I cannot recall exactly what the error messages said. This may have been a result of me stopping it earlier with Ctrl-C, then restarting it. The only thing different about the restart was a long pause before it began. Before I stop one of these, I check to see if [I]nfs.dat[/I] is present. If it is then I know I can stop it if needed. I had never seen this behavior before.