[QUOTE=Dubslow;304303]The DB agrees with that post. Is it you or Clifford who brought it up to that point?[/QUOTE]
It was me all the way, it is a merger with 6^7=279936, and I am working few 6^x with small x (now only 6^7 and 6^9 unsolved). See the reservation thread starting with post 79.

[URL="http://factordb.com/sequences.php?se=1&eff=2&aq=555084&action=last&fr=0&to=100"]555084[/URL] terminates (max height 114).

Nice! Snap for Batalov!:smile:
How do you find them? :razz:
Tell me which one from the remaining terminates fastest, so I can work that one...

Just dumb luck, I guess.

[QUOTE=Dubslow;304523]
--Additionally, as kar_bon suggested, the script now tracks the FDB ID of the last line, and once a week I run a script to check for any duplicates, i.e. merges. Also like he mentioned, the major flaw is that if a merged pair is updated between when I get the first branch and get the second branch, then the merge won't be detected. (It will take a week for the ID list to be fully populated.) (If you look hard enough, the ID is available for each sequence.)
[/QUOTE]

Well, it's been a week and I just ran the merge-detector for the first time. I'm glad kar_bon suggested it, because there's three right off the bat.
[code]bill@Gravemind:~/bin/py∰∂ alimerge.py
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=832314&action=last20&fr=0&to=100"]832314[/URL] and [url=http://factordb.com/sequences.php?se=1&aq=889908&action=last20&fr=0&to=100]889908[/url] seem to have merged.
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=493410&action=last20&fr=0&to=100"]493410[/URL] and [URL="http://factordb.com/sequences.php?se=1&aq=228522&action=last20&fr=0&to=100"]228522[/URL] seem to have merged.
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=594228&action=last20&fr=0&to=100"]594228[/URL] and [URL="http://factordb.com/sequences.php?se=1&aq=38208&action=last20&fr=0&to=100"]38208[/URL] seem to have merged.[/code]
I'll make the necessary adjustments to my page. I manually confirmed each of these with the FDB. Between these three and Batalov's most recent termination, we're now down to 9225 open ended sequences < 1,000,000.

I have decided to run this script once a day, rather than once a week, and depending on my whimsy (or any requests from you folks) I'll run it more often.

[QUOTE=Dubslow;305413]Well, it's been a week and I just ran the merge-detector for the first time. I'm glad kar_bon suggested it, because there's three right off the bat.
[code]bill@Gravemind:~/bin/py∰∂ alimerge.py
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=832314&action=last20&fr=0&to=100"]832314[/URL] and [url=http://factordb.com/sequences.php?se=1&aq=889908&action=last20&fr=0&to=100]889908[/url] seem to have merged.
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=493410&action=last20&fr=0&to=100"]493410[/URL] and [URL="http://factordb.com/sequences.php?se=1&aq=228522&action=last20&fr=0&to=100"]228522[/URL] seem to have merged.
13:53:57 [URL="http://factordb.com/sequences.php?se=1&aq=594228&action=last20&fr=0&to=100"]594228[/URL] and [URL="http://factordb.com/sequences.php?se=1&aq=38208&action=last20&fr=0&to=100"]38208[/URL] seem to have merged.[/code]
I'll make the necessary adjustments to my page. I manually confirmed each of these with the FDB. Between these three and Batalov's most recent termination, we're now down to 9225 open ended sequences < 1,000,000.

I have decided to run this script once a day, rather than once a week, and depending on my whimsy (or any requests from you folks) I'll run it more often.[/QUOTE]

Have you checked these sequences with aliqueit to make sure they aren't broken?

[QUOTE=henryzz;305423]Have you checked these sequences with aliqueit to make sure they aren't broken?[/QUOTE]

I have now :smile:

Of slight interest:
[code]Verifying elf 594228
Verifying index 1644... Sequence merges with earlier sequence 459418.[/code]

[strike]Three[/strike] Two* of these are well known (check the table). Why were you even checking them?

The 889908 -> 832314 is new (at 889908:i4 = 2694160). That's a nice one.

____
* I didn't notice that you reported 594228 twice.

[QUOTE=Batalov;305444]Three of these are well known (check the table). Why were you even checking them?

The 889908 -> 832314 is new (at 889908:i4 = 2694160). That's a nice one.[/QUOTE]

Well then they somehow didn't make it into schickel's last report.

I use the table data from my webpage, which in turn got its initial list of 9231 sequences from AllSeq.txt.

Since then, you've created two terminations, you had another merge with 3366, and the three merges above, two of which were apparently known but missed AllSeq.txt. (The version of AllSeq I started with was in the reservations thread, which has been recently cleaned...)

594228 and 493410 were not in the recent AllSeq.txt. They were only in the old one. Also, my count of open sequences is 9226.

EDIT: added the merge to the post [I]#2[/I] (due to its size at merge). Frank, you can move it to post #1 but let's just not have it there twice.

I probably won't reply to each message individually, but here is a general reply to the above messages.

I believe I started out the AllSeq list by scraping kar_bon's list from his RieselPrime.de [URL="http://rieselprime.de/Others/AliquotIntro.htm"]page[/URL]. At the point I started pulling a (semi-)regular status on everything, I deleted our terminations and merges from the list as they occurred. I noticed that my count tracked Wolfgang's count to within +/- 1, but I figured that was OK because he wasn't always updating immediately.

I [I]thought[/I] I was keeping up to date with everything as we went, but I noticed that I ended up +2 from Wolfgang's count and could never figure out why.

I'll have to sit down and update the list from everything discovered here. If I find any problems, I'll offer a "double your money back" guarantee[SUP]*[/SUP] to anyone who was affected by the errors.

[sup]*[/sup][SIZE="1"]Double money back includes only the amount paid for the AllSeq.txt file. Internet access charges, SMS fees, text or data overages, electricity used while factoring already factored numbers, pain and suffering damages, time spent waiting for the FactorDB to reset your query/page/ID creation counters, and/or any incidental fees are not covered. Not available in all areas, Do not fold, staple, spindle, or mutilate. Equal opportunity employer. Void where prohibited by law. Do not remove under penalty of law. Not all sizes or colors are available in all styles.[/SIZE]