Thank you for the responses to my query.

I have posted several factors to the db over the last couple of days and now see how it works.

In the "big picture" my musings are probably quite insignificant, but thanks for allowing me to provide them.

Perhaps I will try to do more if I can get a better understanding of the software everyone else is using and break away from my personal programming interests.

Should I still provide factors I run across to the db, or does it really matter when someone takes up working on that sequence again? At least for now, I will not be providing any factors larger than 20 digits; 10 digits in the very short term.

Take Care,
Ed

[quote=EdH;198336]Should I still provide factors I run across to the db, or does it really matter when someone takes up working on that sequence again? At least for now, I will not be providing any factors larger than 20 digits; 10 digits in the very short term.[/quote]
Factors that small are very easy (seconds at most) to find when you use efficient tools, so it wouldn't help too much for you to submit them to the DB. Don't bother. It's probably more trouble than it's worth.

[URL="http://factordb.com/search.php?se=1&aq=737490&action=last20&fr=&to="]737490[/URL] terminates
[URL="http://factordb.com/search.php?se=1&aq=738678&action=last20&fr=&to="]738678[/URL] : size 101, 2^2*7

sequence 728490 escaped 2^2*7 directly to the downdriver at i=507, sz. 109.

After two short downdriver runs (down to ~c75) it went back up to c108.

Releasing the sequence at i=1278, size 108, 2^3 (stable), so an interesting sequence is up for grabs.

BTW: I'd recommend QS for the c89 cofactor, as GNFS (using factMsieve.pl) failed:

[code]commencing linear algebra
read 247 cycles
cycles contain 798 unique relations
read 798 relations
using 20 quadratic characters above 26579724
building initial matrix
memory use: 0.2 MB
read 247 cycles
matrix is 5032 x 247 (0.0 MB) with weight 12263 (49.65/col)
sparse part has weight 7549 (30.56/col)
matrix is corrupt; skipping linear algebra
elapsed time 00:00:04
Some error occurred and matsolve did not record dependencies.
WARNING: gnfs failed to find a factor. This really shouldn't happen.
I'll just run ecm till the end of time or a factor turns up...
Let's hope you don't run out of disk space before either of those.
running 0 auto-increasing ecm curves...[/code]

Edit: reserving 734088

unreserving 729624 at i=1010, size 130 (oops...), [COLOR="Red"]2³*3*5[/COLOR]

Edit: reserving 734112

[quote=Andi47;198369]BTW: I'd recommend QS for the c89 cofactor, as GNFS (using factMsieve.pl) failed:

[code]matrix is corrupt; skipping linear algebra[/code][/quote]
I'm pretty sure a little more sieving would let you finish this one, if you've still got the files and are interested in finishing off that c89.

[QUOTE=Mini-Geek;198378]I'm pretty sure a little more sieving would let you finish this one, if you've still got the files and are interested in finishing off that c89.[/QUOTE]

I'm pretty sure too, but I currently don't have the personal time to do so...

unreserving 734088 at size 102, 2^5*3^3*5^2

reserving 734184

Done with 739032, 107 digits, 2*3*5*7

730656: i444->i904, size 110, 2^3*3^2*5*7
736002: i685->i3585, size 110, 2^4*3^4*31
unreserving both

Done with 736944 737034 737160 737240 737550 737664,
but will keep [I]737160 reserved[/I] for a bit longer.

Reserving 734520, 734592, 734676, 734760 - let's finish that 5K.