[QUOTE=VBCurtis;472681]I'm trying to learn CADO's knobs and buttons, and a steady supply of sub-150 digit GNFS candidates is useful for this. I've been cracking fivemack's fully-ECM'ed dropped reservations for the last week or so; is this bad form? I do not run the sequences after factoring his stopping point.

If one ever does something interesting, I'll PM Mr Womack with details.[/QUOTE]


That's absolutely fine, it's why I point out that my abandoned numbers have been fully-ECMed; I encourage you to run the sequences at least a little further if you have the cycles and there is the slightest sign of anything interesting, if only because leaving a C130 cofactor in the table when it has a 20-digit factor feels a bit messy.

Dropping 1435200 2^7*3^5*5 fully ECMed C134

Reserving 1645584

Dropping 1715310: 2^2 * 3 * 7 * ECMed C128

Drop 1700190 1697274 1761504 1674276 1706418 1685358 1652616 1740948 1757784 1753290 1744734 1749916 1720800 1705320 1724880 1736868 1759200 1673406 1753254 1580976 1749744 1751904 1553160 1684200
Reserve 1743624 1898760 1932360 1875342 1988352 1590612 1957788 1969880 1969060 1629480 1635576 1585800 1940940 1622400 1885512 1851114 1970496 1632420 1382500 1414944 1416360 1437060 1454610 1468200 1476744

Dropping 1529136, 1800486.

Dropping 1600844 (2^2*3, ECMed C112)

Taking 1360608

Does the script which updates reservations also cause the sequences which have been reserved or unreserved to be rescanned? I think it probably should.

[QUOTE=fivemack;472861]Does the script which updates reservations also cause the sequences which have been reserved or unreserved to be rescanned? I think it probably should.[/QUOTE]

Not directly, no, though as I recall ChristianB told me he was using a secondary script to update reserved sequences faster.

It's not a bad idea overall. I'll try to incorporate it (or some variant) into the new overhaul of the scripts I've been working on.

Dropping 1424688 (2^6 * 3 * 127 * ECMed C122)

Taking 1481094 1235394