9m5_263 factored
 

[code]
p71 factor: 12047148139352766754859725045952250501198736783793080325577218673476201
p158 factor: 12199899427634326767083034694090485186756744665386819009946581419641447176080150003216079386485607377817166862017661902632438072206873701021584228886114023169
[/code]

[url]https://pastebin.com/Y66XBeb7[/url]

Taking 11p4_241.

Taking 11m9_241

11m4_241 done
 

[code]
Tue Jul 16 12:17:24 2019 p81 factor: 301173663591011981702459592937500069687148929453759118435772328764749977349309657
Tue Jul 16 12:17:24 2019 p161 factor: 22363515223598628720938528891665396897518826441414996942606123583370915836131172930865697150339547925226853527820061658889322372469223124458917446020040006633947
[/code]

88.4 hours on 4 cores i7/4790K for 12.14M matrix at density 122 (not 124), built from 191359438 unique relations out of 258090086 legible ones.

Log attached and at [url]https://pastebin.com/tUp7r8MX[/url]

Taking C220_M31_k84

C205_M31_56
 

[QUOTE=richs;521597]Taking C205_M31_56[/QUOTE]

The attached fb file (renamed to .txt to allow upload) downloaded from NFS@home is incorrect:

[CODE]Wed Jul 17 19:09:47 2019
Wed Jul 17 19:09:47 2019
Wed Jul 17 19:09:47 2019 Msieve v. 1.54 (SVN 1018)
Wed Jul 17 19:09:47 2019 random seeds: a04eb644 ffb8de94
Wed Jul 17 19:09:47 2019 factoring 206096410611951174045821265662801553998153606775865027340583623737504752836950161480307306091972044325136654318470634270970481119615373216127224716703050950135265027468900620513606317179638695800547135347262644369289055809 (222 digits)
Wed Jul 17 19:09:49 2019 searching for 15-digit factors
Wed Jul 17 19:09:52 2019 commencing number field sieve (205-digit input)
Wed Jul 17 19:09:52 2019 warning: NFS input not found in factor base file
Wed Jul 17 19:09:52 2019 R0: 0
Wed Jul 17 19:09:52 2019 A0: 0
Wed Jul 17 19:09:52 2019 skew 1.00, size 0.000e+000, alpha 0.000, combined = 0.000e+000 rroots = 0
Wed Jul 17 19:09:52 2019
Wed Jul 17 19:09:52 2019 commencing relation filtering
Wed Jul 17 19:09:52 2019 setting target matrix density to 120.0
Wed Jul 17 19:09:52 2019 warning: NFS input not found in factor base file
Wed Jul 17 19:09:52 2019 estimated available RAM is 4043.9 MB
Wed Jul 17 19:09:52 2019 commencing duplicate removal, pass 1
[/CODE]

Would someone kindly post the correct fb file? Thanks!

[QUOTE=richs;521834]The attached fb file (renamed to .txt to allow upload) downloaded from NFS@home is incorrect:

[CODE]Wed Jul 17 19:09:47 2019
Wed Jul 17 19:09:47 2019
Wed Jul 17 19:09:47 2019 Msieve v. 1.54 (SVN 1018)
Wed Jul 17 19:09:47 2019 random seeds: a04eb644 ffb8de94
Wed Jul 17 19:09:47 2019 factoring 206096410611951174045821265662801553998153606775865027340583623737504752836950161480307306091972044325136654318470634270970481119615373216127224716703050950135265027468900620513606317179638695800547135347262644369289055809 (222 digits)
Wed Jul 17 19:09:49 2019 searching for 15-digit factors
Wed Jul 17 19:09:52 2019 commencing number field sieve (205-digit input)
Wed Jul 17 19:09:52 2019 warning: NFS input not found in factor base file
Wed Jul 17 19:09:52 2019 R0: 0
Wed Jul 17 19:09:52 2019 A0: 0
Wed Jul 17 19:09:52 2019 skew 1.00, size 0.000e+000, alpha 0.000, combined = 0.000e+000 rroots = 0
Wed Jul 17 19:09:52 2019
Wed Jul 17 19:09:52 2019 commencing relation filtering
Wed Jul 17 19:09:52 2019 setting target matrix density to 120.0
Wed Jul 17 19:09:52 2019 warning: NFS input not found in factor base file
Wed Jul 17 19:09:52 2019 estimated available RAM is 4043.9 MB
Wed Jul 17 19:09:52 2019 commencing duplicate removal, pass 1
[/CODE]

Would someone kindly post the correct fb file? Thanks![/QUOTE]

I don't know who posted this composite, but the .fb (and .poly) files are a little strange. The given N value has a couple of small factors, and I've no idea where the skew value comes from.

But with that said, I don't understand my msieve is complaining the way it is. The .fb file does appear to have a valid number and polynomial; I just would have thought that it would find the small factors while "searching for 15-digit factors". What exact command line are you using?

msieve does find the small factors; this means the number it's looking at no longer matches the msieve.fb file and it complains at that stage.

I'd replace the first line with

[code]
N 7387537286900905815401063314500552382322057964368137200467347228657034281431673240267264397437745991785922791711680613214831602148453688733085622897860252661860028465100882538081348091993504514351219704193
[/code]

There is also something else odd with the file attached, it has a blank line between each valid line, but that's not the case when I download [url]https://escatter11.fullerton.edu/nfs_data/C205_M31_56/C205_M31_56.fb[/url] directly

C205_M31_56
 

I posted C205_M31_56, with a polynomial generated on the [url=http://cownoise.com/]cownoise site[/url]. This site generates a generic poly based on its internal values, so N in the poly file sometimes contains known small factors (though they are unknown to cownoise). I usually replace N with the correct composite as Fivemack suggests but I missed it here. AIUI, the poly is correct but inefficient, and msieve isn’t happy with it once the small factors are found.

As to the skew it’s what cownoise spit out. Interesting question.

As to the mysterious space appearing in the .fb file, I often see this on my Windows boxes. Windows appears not to handle line breaks generated by some of the factoring tools.

richs - did you replace N in the .fb file as Fivemack suggested? That should stop msieve’s complaints.

C205_M31_56
 

Msieve is now running fine after I replaced N in the fb and worktodo files. Thanks for the advice.

Taking 12p5_233.