YAFU 2.0

[BudgieJane]

Originally Posted by bsquared

Actually, I'm wrong, you have to have one -v for it to *say* that it parsed the .ini file. It will parse it correctly regardless of what it says, it's just a reporting problem.

So the workaround is to do nothing. I can live with that.

Thank you.

[ConceptJunkie]

So, in general, I discovered, completely by trial and error, that when YAFU crashes on a particular number, it will usually work if you increase rhomax enough in yafu.ini.

I use a value of 1000 by default, but occasionally come across numbers that will crash yafu until I increase it to 10000, 20000 or even 100000. I usually use yafu to look for long aliquot sequences, and seldom factor numbers larger than about 100 digits.

As a novice, I don't know what that setting actually does, besides making factoring take a bit longer, but for fellow novices, I thought it was worth mentioning.

[storm5510]

I would like to find some documentation as to how to use it.

[kruoli]

With the current version, I still get matrix must have more columns than rows in SIQS sometimes.
Example:

starting SIQS on c81: 422751689472424067829539206601508400436611125331139179502143148987658541073541313
random seed: 17192571071955053739

[kruoli]

Originally Posted by storm5510

I would like to find some documentation as to how to use it.

Do you mean this?

[storm5510]

Originally Posted by kruoli

Do you mean this?

That would be it. I have problems navigating Github for some reason.

[James Heinrich]

Just a suggestion that would be (very) useful to me, perhaps others: output results in JSON format. I'm thinking something along the lines of:

{
  "input-expression":"2^123/17",
  "input-decimal:"625519056839960410778262146014279800",
  "factors-prime":["2","2","2","3","3","5","5","7","11","13","31","41","61","151","241","331","1321"],
  "factors-composite":["281406274007041"],
  "ecm-curves":{"2000":30, "11000":74, "50000":216, "250000":432},
  "ecm-levels":{"t15":38.02, "t20":11.32, "t25":1.06, "t30":0.07, "sum":25.34},
  "time-start":"2022-04-25 16:25:34",
  "time-end":"2022-04-25 18:34:56",
  "runtime":{"total":7762.123, "ecm":762.456, "pm1":16.95, "siqs":7654.32}
}

(most of the above is made up for demonstration purposes)
The idea being to make a consistent, easily-parsable output format that can contain all the relevant information in one place. Undoubtedly there are some other values that can/should be included, the beauty is they can be added (or be missing) without breaking any parsing.
Obviously this output is only sane when an assignment is completed and can't be output during runtime as is done to factor.log but it would be an additional output.

[kruoli]

While James's suggestion might be a lot of work, I find it tremendeous! Especially the example is really neat in regards to which data might/can be included.

[bsquared]

A lot of this info is fairly easily available at the end of a factorization:

cat factor.json
{
        "input-expression":"factor(2^351-1)",
        "input-decimal":"4586997231980143023221641790604173881593129978336562247475177678773845752176969616140037106220251373109247",
        "factors-prime":["7","73","79","937","6553","8191","86113","29121769","7830118297","571890896913727","93715008807883087","150832426800173710177","446473","121369"],
        "factors-composite":["262657"],
        "ecm-levels" : [],
        "runtime" : ["total":0.4672, "ecm":0.0000, "pm1":0.0133, "pp1":0.0000, "siqs":0.0421, "nfs":0.0000],
}
{
        "input-expression":"factor(2^371-1)",
        "input-decimal":"4809815209520810450717656262224562232065397860164239095208531909697964083434718092213655548692006303809402830847",
        "factors-prime":["127","743","2969","6361","69431","20394401","63781899287","204712366597949333831","145980337155634444285232523876979318451464756266456641329"],
        "ecm-levels" : ["t15":43.89,"t20":12.78,"t25":1.18,"t30":0.07],
        "runtime" : ["total":3.3807, "ecm":1.8949, "pm1":0.5183, "pp1":0.0000, "siqs":0.0000, "nfs":0.0000],
}

That's what I have so far. All I know about JSON comes from looking at James's post, so keep that in mind. I'm basically just copying the formatting I saw. If something is broken let me know. The good thing is that this is an extra file, and won't break anything else. I can keep looking for low-hanging fruit to add to the output.

[James Heinrich]

Originally Posted by bsquared

That's what I have so far. All I know about JSON comes from looking at James's post

That's great!

Wikipedia of course has a decent rough overview of JSON syntax.
And looking at that I see I made a mistake in my example: arrays (with no explicit keys, such as the list of factors) are specified with square brackets, but objects (in my example used as arrays with named keys) should be specified with curly braces.
So "ecm-curves", "ecm-levels", "runtime" should change from [square] to {curly}. Sorry about that.


edit: I'm not sure why "factors-composite":["262657"], shows in your first example since that's prime. Or perhaps this was just a hand-edited example?

[bsquared]

Originally Posted by James Heinrich

That's great!

Wikipedia of course has a decent rough overview of JSON syntax.
And looking at that I see I made a mistake in my example: arrays (with no explicit keys, such as the list of factors) are specified with square brackets, but objects (in my example used as arrays with named keys) should be specified with curly braces.
So "ecm-curves", "ecm-levels", "runtime" should change from [square] to {curly}. Sorry about that.


edit: I'm not sure why "factors-composite":["262657"], shows in your first example since that's prime. Or perhaps this was just a hand-edited example?

Thanks for the fix! I'm reading the syntax page but I will likely rely heavily on users to tell me when things are broken. The composite example was actually a bug... it's now fixed.

 cat factor.json
{
        "input-expression":"factor(2^351-1)",
        "input-decimal":"4586997231980143023221641790604173881593129978336562247475177678773845752176969616140037106220251373109247",
        "input-argument-string":"factor(2^351-1) -v ",
        "factors-prime":["7","73","79","937","6553","8191","86113","262657","29121769","7830118297","571890896913727","93715008807883087","150832426800173710177","446473","121369"],
        "pm1-curves" : {"150000":1},
        "runtime" : {"total":0.5976, "ecm":0.0000, "pm1":0.0149, "pp1":0.0000, "siqs":0.0418, "nfs":0.0000},
        "time-start" : "2022-05-04  13:26:58",
        "time-end" : "2022-05-04  13:26:59",
}
{
        "input-expression":"factor(2^371-1)",
        "input-decimal":"4809815209520810450717656262224562232065397860164239095208531909697964083434718092213655548692006303809402830847",
        "input-argument-string":"factor(2^371-1) -v -plan deep ",
        "factors-prime":["127","743","2969","6361","69431","20394401","63781899287","204712366597949333831","145980337155634444285232523876979318451464756266456641329"],
        "pm1-curves" : {"150000":1},
        "ecm-curves" : {"2000":48,"11000":96,"50000":214},
        "ecm-levels" : {"t15":40.03,"t20":11.50,"t25":1.06,"t30":0.07},
        "runtime" : {"total":1.4576, "ecm":0.4515, "pm1":0.0472, "pp1":0.0000, "siqs":0.0000, "nfs":0.0000},
        "time-start" : "2022-05-04  13:27:07",
        "time-end" : "2022-05-04  13:27:08",
}