Sequence terminations and merges

[unconnected]

2762208 terminates

[Aillas]

2653632 (i3097) merges with 1533822 (i123)

[unconnected]

628392(i2735) = 1486380(i2)

[unconnected]

2744952 terminates!
My first termination for a while.

[Batalov]

2698194 merged with 4800

[Aillas]

2672516 (i3189) merges with 1467194 (i0)

[gd_barnes]

Originally Posted by Aillas

2672516 (i3189) merges with 1467194 (i0)

Originally Posted by Aillas

2571060(i3479) merge with 2086732(i0)

Originally Posted by Aillas

2603574 (i2881) merge with 1538078 (i0)

Originally Posted by Aillas

2579248 (i4715) merged with 1561730 (i0)

All of these sequences were terminated at the time that they were posted. Other people typically report such sequences as terminated instead of merged regardless of how low they dropped before terminating. Stating that they merged in this thread gives the impression that they did not terminate.

The merge info that aliquet.exe states should be ignored as it is not reliable even if the sequence does not terminate. Usually there is a smaller sequence that is the correct merge than what aliquet.exe states.

Someone please correct me if I'm wrong about this.

[Happy5214]

Originally Posted by gd_barnes

The merge info that aliquet.exe states should be ignored as it is not reliable even if the sequence does not terminate. Usually there is a smaller sequence that is the correct merge than what aliquet.exe states.

That aliqueit feature has always been poorly executed, and I disabled it long ago. My rule is if it gets below 10 digits or thereabouts and starts going back up, I'll stop it manually, upload to FactorDB, and check there for a merge/termination.

[Aillas]

Originally Posted by gd_barnes

All of these sequences were terminated at the time that they were posted. Other people typically report such sequences as terminated instead of merged regardless of how low they dropped before terminating. Stating that they merged in this thread gives the impression that they did not terminate.

The merge info that aliquet.exe states should be ignored as it is not reliable even if the sequence does not terminate. Usually there is a smaller sequence that is the correct merge than what aliquet.exe states.

Someone please correct me if I'm wrong about this.

If aliquet.exe says the sequence has merged with another one, I already verify the merge first by using the tools AliMerge.
If it doesn't found a merge (only works with seq > 80 digits), then I use the merge info provided by aliqueit.
Maybe I should provide more info when verifying using alique.exe merge data and say if it's just a merge or a merge+termination

[gd_barnes]

Originally Posted by Aillas

If aliquet.exe says the sequence has merged with another one, I already verify the merge first by using the tools AliMerge.
If it doesn't found a merge (only works with seq > 80 digits), then I use the merge info provided by aliqueit.
Maybe I should provide more info when verifying using alique.exe merge data and say if it's just a merge or a merge+termination

Less info is better. Use the FactorDB as your first guide before looking at any merge info.

When you enter the sequence in the FactorDB, if the sequence is terminated, just simply state in this thread that sequence XXXXXXX terminates. There's no reason to say anything about a merge.

If the FactorDB does not show that the sequence has terminated, then use whatever tool works best for you (but not aliquet.exe) to state here what sequence that it merges with. Aliquet.exe merge info is not reliable.

In effect, this is what everyone else here has been doing. See the many terminations by Batalov and unconnected in this thread.

[Batalov]

2931396 merges with 36792