...and he released without noticing it!
[QUOTE=unconnected;332971]I'm done with 87348, 883554, 738546, 407856.[/QUOTE]
Dima, you have to be more attentive! :smile:

Whoops, what a surprise! :smile:
I've rechecked my logs - aliqueit didn't detect merge.

[QUOTE=unconnected;333490]Whoops, what a surprise! :smile:
I've rechecked my logs - aliqueit didn't detect merge.[/QUOTE]
I might be missing something, but doesn't Aliqueit only detect the new index falling below the original number as a merge?

The old db used to display these other merges, but the new one hasn't had this feature implemented, yet.

Yes, the onus is on the researcher. It is tricky, but it can be done.

For example, if one of my sequences goes reasonably deep and then climbs up to, say, c70s, it is a good idea to submit it right then. After submission, check what the database would show - and if it would show a c115 or larger, then you happily kill the running process and start checking to what sequence it merged. [SIZE=1](which in itself is a separate story, left as an exercise to the reader; one hint would be to use Bill's "status database")[/SIZE]

[QUOTE=Batalov;333492]Yes, the onus is on the researcher. It is tricky, but it can be done.

For example, if one of my sequences goes reasonably deep and then climbs up to, say, c70s, it is a good idea to submit it right then. After submission, check what the database would show - and if it would show a c115 or larger, then you happily kill the running process and start checking to what sequence it merged. [SIZE=1](which in itself is a separate story, left as an exercise to the reader; one hint would be to use Bill's "status database")[/SIZE][/QUOTE]

[QUOTE=EdH;333491]I might be missing something, but doesn't Aliqueit only detect the new index falling below the original number as a merge?

The old db used to display these other merges, but the new one hasn't had this feature implemented, yet.[/QUOTE]
Indeed.

If Jatheski hadn't been looking, I'm reasonably confident that I would have detected it within a week -- I have a script that checks my page daily for merges. (I'll leave this merge in my page for now as a test of my confidence. :smile:)

Another success - [URL="http://factordb.com/aliquot.php?type=1&aq=738288&big=1"]738288[/URL] terminates this morning.

[QUOTE=unconnected;333701]Another success - [URL="http://factordb.com/aliquot.php?type=1&aq=738288&big=1"]738288[/URL] terminates this morning.[/QUOTE]
hip! hip!
congrats!

Hmmmm....as Arte Johnson would say "Verrrry interesting....":

From 05-Oct-09:[QUOTE=Batalov;191983]Time to clean up the attic. Releasing
[CODE]....
247296 1404 106 [COLOR=red]2^2 * 7[/COLOR]
....[/CODE][/QUOTE]From 09-Oct-12:[QUOTE=Dubslow;314090]There are [strike]170[/strike] 165 with index > 1000, [strike]but it's likely that many of these are in fact beyond.[/strike] I'll manually check when it's down to around 50 or so.
Edit: Cross edit :razz: It seems you know slightly more than I do. Which 5 are past 113?
[code]....
247296 1471. sz 113 2^2 * 7 * C112
....[/code][/quote]From 12-Mar-13[QUOTE=fivemack;333086]3xxxxx is pretty much done.

So I'd like to reserve 1xxxxx and 2xxxxx, to keep the Xeons from getting cold since I'm about to leave the country for a few weeks.
....
247296
....[/quote]Today (13-Apr 13):[QUOTE=RobertS;336937]Releasing 630660, 857718
Taking 247296

PS: Have added already 2500 lines, but now there are much more lines in the DB.

PPS: 467658 merges with 247296 and so releasing it :whistle:[/QUOTE]Does your automation keep detailed logs, Tom? (So we can figure out a date...) (And maybe you should add an alert if something gets down below ~12 digits or so.....)

Officially: [B]467658:i10 = 247296:i3037 = 410529720[/B]!!!!!

So we had another sequence go up and come back down to merge with a higher sequence.....pretty cool. (So far Dubslow's spider has not picked up the extension of 247296....)

I haven't started 247296 yet: I just drop the numbers into a hopper and run make -j8 on an eight-core machine. I've removed it from the hopper and am leaving it to RobertS.

190128, on the other hand, terminates

(2884 iterations to get to prime 601; highest was 119 digits at iteration 1435)

311202 tmerge with 218966 after 2718 iteration and reaching a heigt of 121 digits
218966 terminate @ 43 after an handfull of iteration