You can learn SNFS in a few minutes; it's not exactly a commitment.
34*10^195-61 = 34x^5 - 61. What is x?
That's it.
Set m = the x-value you figure out, c5 = 34, c0 = -61. Done. The factorization would take a quad-core a day, maybe?

Edit: "m" is how ggnfs/msieve records that value. I think CADO needs the rational poly spelled out, so you'd use R1 = 1, R0 = m, or -m (trial and error? Not sure what exact names CADO uses for these, but there's a sample included with the package)

I recall the sticking point was converting GGNFS form to CADO poly form via convert_poly and my best judgement for the mapping between GGNFS parameters and CADO's; I did not keep the logfile to indicate where it failed.

Thanks for the quick demo on SNFS polynomial selection for numbers of this form---x is of course 10^39, and for 34*10^196-61, x would be 10^49 for a quartic polynomial, or c5 = 340 and x = 10^39 -- the smaller value of m being preferred over a lower-degree polynomial.

I'll abstain from this thread until I'm more sure I have something more useful to contribute.

A pleasant combination of a light summer teaching load and a shiny new-to-me 20-core Xeon box has me resuming my parameter optimation work for CADO. I'm pleased to say that while 10 threads solve a matrix from the 15e queue, I can still crack a C145 in under 24hr on this single machine.

I'm going through the aliquot sequence thread, factoring every fully-ECM'ed composite mentioned in an un-reservation in 2018. I expect to have new params files for c115 through c150 within a week or two; I'll post them to this thread in hopes some of you will test them against default CADO or against msieve/GGNFS (yafu or factmsieve or your own custom params).

If anyone has GNFS inputs in the 130s they'd like me to solve, I'll be happy to factor a few. It seems there are few released sequences with ECM'ed cofactors in the 130s, so I don't have much data on jobs that size.

[QUOTE=VBCurtis;492504]If anyone has GNFS inputs in the 130s they'd like me to solve, I'll be happy to factor a few. It seems there are few released sequences with ECM'ed cofactors in the 130s, so I don't have much data on jobs that size.[/QUOTE]
A post from a different thread.
[QUOTE=hyramgraff;492435]Since you're asking about numbers that are ready for SNFS I thought I should mention that just last week I finished running 45 digit ECM on all of the C130-C139 numbers in [URL="https://gitlab.com/hyramgraff/odd-perfect-ecm/blob/e2ecd2a115d7ed06c39aaf11bc241dd0ca56639a/t2100.txt"]this [/URL]version of the t2100 file. I believe that they are now ready for SNFS.[/QUOTE]
Actually these are mostly GNFS jobs. The t2100 file can be found at [url]http://www.lirmm.fr/~ochem/opn/t2100.txt[/url] or linked from Pascal's OPN homepage at [url]http://www.lirmm.fr/~ochem/opn/[/url]

I clicked on those links, and didn't find the file format easily grokked in terms on which should be GNFS and which should be SNFS. Aliquot terms are much simpler for me to grab, ECM pretest, and run.

I'm on break from refining parameters, as I've fired up a GNFS 180 on CADO. I'm quite impressed with I=15 siever performance:
32/33LP, 64/95 MFB, 60M/100M factor base bounds. Q=10-18M so far has produced over 100M relations! That's a yield of.... twelve. ETA is around 3 weeks to harvest 450M relations (CADO default target). CADO does not provide timing data, but some hand timing of individual 1k ranges tested on client machines indicates around 0.1 sec/relation.
It's possible that CADO is *much* more efficient using 3LP than GGNFS sievers. That would explain their params files using 3LP some 30 digits lower than we traditionally have!
Once it enters the matrix phase, I'll zcat all the rels files to an msieve instance and compare matrix ETA forecasts. I expect msieve will be much quicker for the matrix, and that I'll manage a GNFS 180 sieve + LA on personal machines in under a calendar month!

If anyone is in the mood to test CADO out some more, please request params files; I have updated files for 105-145, still experimenting with looser LP bounds (occasionally a great improvement, but timings vary more from input to input). I think I've improved 115 and 120 files 10% from my previous submissions.

I'm playing with cado-nfs again and I have some data for a c156 run below. My farm is only about half its size from before and many of those are throttling due to heat.

I wouldn't mind having the optimum params for the sizes I don't yet. I'm probably going to be playing with my hybrid setup (cado-nfs/msieve) more so than completing with cado-nfs. But, if you have a particular request, let me know and I'll run a pure cado-nfs session.

This c156 used your c155 enhanced params:
[code]
Info:Polynomial Selection (size optimized): Aggregate statistics:
Info:Polynomial Selection (size optimized): potential collisions: 150312
Info:Polynomial Selection (size optimized): raw lognorm (nr/min/av/max/std): 151793/47.410/56.749/62.720/1.079
Info:Polynomial Selection (size optimized): optimized lognorm (nr/min/av/max/std): 151793/46.330/50.825/57.370/1.514
Info:Polynomial Selection (size optimized): Total time: 295917
Info:Polynomial Selection (root optimized): Aggregate statistics:
Info:Polynomial Selection (root optimized): Total time: 14779.5
Info:Polynomial Selection (root optimized): Rootsieve time: 14778.1
Info:Generate Factor Base: Total cpu/real time for makefb: 37.33/8.10258
Info:Generate Free Relations: Total cpu/real time for freerel: 2466.57/322.135
Info:Lattice Sieving: Aggregate statistics:
Info:Lattice Sieving: Total number of relations: 139321222
Info:Lattice Sieving: Average J: 8229.15 for 1556330 special-q, max bucket fill: 0.629541
Info:Lattice Sieving: Total CPU time: 5.94073e+06s
Info:Filtering - Duplicate Removal, splitting pass: Total cpu/real time for dup1: 756.79/462.649
Info:Filtering - Duplicate Removal, splitting pass: Aggregate statistics:
Info:Filtering - Duplicate Removal, splitting pass: CPU time for dup1: 462.3s
Info:Filtering - Duplicate Removal, removal pass: Total cpu/real time for dup2: 2275.86/656.124
Info:Filtering - Singleton removal: Total cpu/real time for purge: 884.42/348.291
Info:Filtering - Merging: Total cpu/real time for merge: 1805.72/1607.63
Info:Filtering - Merging: Total cpu/real time for replay: 200.41/181.724
Info:Linear Algebra: Total cpu/real time for bwc: 822208/0.000218153
Info:Linear Algebra: Aggregate statistics:
Info:Linear Algebra: Krylov: WCT time 68695.93
Info:Linear Algebra: Lingen CPU time 1900.97, WCT time 291.16
Info:Linear Algebra: Mksol: WCT time 37246.96
Info:Quadratic Characters: Total cpu/real time for characters: 247.36/69.3931
Info:Square Root: Total cpu/real time for sqrt: 13184.9/1945.28
Info:HTTP server: Shutting down HTTP server
Info:Complete Factorization: Total cpu/elapsed time for entire factorization: 7.09549e+06/172154
Info:root: Cleaning up computation data in /tmp/cado.s0wg3y09
50991922118453733800893403222829283966167525130934549348631327443632984128217423175047 17463527688603612045476003591361612022388344033034895907221918699698189
[/code]

Here's a c123 run with default params:
[code]
Info:Polynomial Selection (size optimized): Aggregate statistics:
Info:Polynomial Selection (size optimized): potential collisions: 21528.1
Info:Polynomial Selection (size optimized): raw lognorm (nr/min/av/max/std): 21720/36.270/43.664/48.210/0.888
Info:Polynomial Selection (size optimized): optimized lognorm (nr/min/av/max/std): 21720/35.540/39.371/44.430/1.211
Info:Polynomial Selection (size optimized): Total time: 2285.24
Info:Polynomial Selection (root optimized): Aggregate statistics:
Info:Polynomial Selection (root optimized): Total time: 1865.24
Info:Polynomial Selection (root optimized): Rootsieve time: 1863.87
Info:Generate Factor Base: Total cpu/real time for makefb: 10.62/2.3481
Info:Generate Free Relations: Total cpu/real time for freerel: 156.16/20.4439
Info:Lattice Sieving: Aggregate statistics:
Info:Lattice Sieving: Total number of relations: 13059349
Info:Lattice Sieving: Average J: 3800.88 for 178693 special-q, max bucket fill: 0.772261
Info:Lattice Sieving: Total CPU time: 149258s
Info:Filtering - Duplicate Removal, splitting pass: Total cpu/real time for dup1: 34.46/59.7937
Info:Filtering - Duplicate Removal, splitting pass: Aggregate statistics:
Info:Filtering - Duplicate Removal, splitting pass: CPU time for dup1: 59.7s
Info:Filtering - Duplicate Removal, removal pass: Total cpu/real time for dup2: 153.42/49.1674
Info:Filtering - Singleton removal: Total cpu/real time for purge: 138.1/36.692
Info:Filtering - Merging: Total cpu/real time for merge: 203.37/175.179
Info:Filtering - Merging: Total cpu/real time for replay: 20.59/17.1169
Info:Linear Algebra: Total cpu/real time for bwc: 11504.3/0.000172377
Info:Linear Algebra: Aggregate statistics:
Info:Linear Algebra: Krylov: WCT time 899.45
Info:Linear Algebra: Lingen CPU time 175.19, WCT time 27.82
Info:Linear Algebra: Mksol: WCT time 515.74
Info:Quadratic Characters: Total cpu/real time for characters: 23.33/6.71058
Info:Square Root: Total cpu/real time for sqrt: 995.39/135.9
Info:HTTP server: Shutting down HTTP server
Info:Complete Factorization: Total cpu/elapsed time for entire factorization: 166648/4008.26
Info:root: Cleaning up computation data in /tmp/cado.8n8o3zi4
103994263537692083322430805948369677781344426601569708601629807617921045503073013 4877573650317223159406644589665201167150419
[/code]

Attached are my current params choices for c115, c120, and c130. I do not plan to tweak c115 any further, but I'm still doing a little tinkering with the bigger files.
I've only done 3 jobs at c125 level, so I don't have a new file for that just yet; I'll get to work this week on that size.

Thanks Curtis,


Now I have to go back and research something, though. My latest run, a c151, which is using your enhanced params.c150, has appeared to have gotten stuck:
[code]
Info:Polynomial Selection (size optimized): Marking workunit c150_polyselect1_184500-185000 as ok (99.2% => ETA Mon Aug 13 21:37:53 2018)
[/code]There is no work being assigned, all clients are in waiting and it doesn't look like the host is doing anything anymore, either. I'll have to see if I can retrieve the restart info and attempt that. I have to go look, though - didn't I have this trouble before?


Ed

Ed-
You did, and I've been putting admin = xxxx settings into c125 and up files since you had that trouble, since it seems that very small starting coeffs sometimes get stuck. Try adding "admin = 8400" directly above the "admax = " line in the file.
Since you use a ton of clients, you may choose to reduce adrange to 840 or 420, so that smaller units of work are distributed. It'll keep more clients fed for more of the poly select phase. Just make sure you use a multiple of 420, since the poly select is 2-threaded and we only search multiples of 210.
That reminds me, I forgot to put admin = 1260 into the c130 params file just above.

[QUOTE=VBCurtis;493844]Ed-
You did, and I've been putting admin = xxxx settings into c125 and up files since you had that trouble, since it seems that very small starting coeffs sometimes get stuck. Try adding "admin = 8400" directly above the "admax = " line in the file.
Since you use a ton of clients, you may choose to reduce adrange to 840 or 420, so that smaller units of work are distributed. It'll keep more clients fed for more of the poly select phase. Just make sure you use a multiple of 420, since the poly select is 2-threaded and we only search multiples of 210.
That reminds me, I forgot to put admin = 1260 into the c130 params file just above.[/QUOTE]
Thanks! I was just going to go search that out. admin was 1e3 and adrange was 5e2. I changed them to 8400 and 420, respectively and restarted from scratch.

I think I'm running 54 clients now, but for some reason, I keep losing some. Since they're in bash generated gnome-terminals, I never catch any crash info. They're just closed and gone.