1934442:[URL="http://factordb.com/sequences.php?se=1&aq=1934442&action=range&fr=2190&to=2194"]i2194[/URL] (after reaching 100d and coming down) merges with 143676:[URL="http://factordb.com/sequences.php?se=1&aq=143676&action=range&fr=0&to=3"]i3
[/URL]

1952670 terminated at i1361.

The seq(s) 1974448 seem(s) to have merged with 1320480

1320480:1340 = 1974448:12

Which sequence do you delete in this case?

Always remove the larger sequence (1974448)

1868148 terminates

The seq(s) 1741632 seem(s) to have merged with 1632

Dubslows code automatically deletes the larger seq when a merge is detected.

(1741632:3912 = 1632:37; I have an auto-reporter meaning that I don't necessarily notice merges as they happen)

That's the right way.
In my DB however, I keep both the "smallest" and the "longest" sequence that reach some composite. In case someone is looking for long sequences.

(my DB entries are [n, s, m, i, z, j, p1, a1, ...], where n is the number, s is its status, m is the smallest sequence reaching n at index i, z is the longest sequence reaching n at index j, and p^a are the factors, except the last (prime or unknown cofactor) - this way mergers are detected automatically, and the same composite is never factored two times)

1211160 terminated

1938060 terminates @ i4415

[URL="http://factordb.com/sequences.php?se=1&aq=1431248&action=last20"]1431248[/URL] merges with [URL="http://factordb.com/sequences.php?se=1&aq=20196&action=last20"]20196[/URL] @ ~ i2300

sequence 1052310 has terminated