[CODE]1536456 <- 2304744
2237562 <- 2610528[/CODE]2237562 should be restored in AllSeq (instead of 2610528)

238 more merges - attached.


(they are simple in that the second number is simply on the path of aliq_seq(number#1) )

Merges:

1870806 <- 2405418
1946352 <- 2158656
1986544 <- 2412480
1853460 <- 2689428
1839894 <- 2431722

Merges:

1469874 <- 2376354
1927992 <- 2818632
1756710 <- 2876490
1854942 <- 2267286
1622988 <- 2759376
1912170 <- 2661618
1740558 <- 2785482
1870386 <- 2404878
1654152 <- 2517048
1838934 <- 2381022

[QUOTE=Batalov;496280]238 more merges - attached.


(they are simple in that the second number is simply on the path of aliq_seq(number#1) )[/QUOTE]

I added this list to the blue page in order to delete the merges but I ended up with new sequences. For example: 736584, 880536, 451710, 990582 and others in the 1e6, 2e6 range.I wonder if this means the list on the blue page is incomplete?

Edit: In the case of 880536 it is because it merges with 831034 at index 377 but this also merges with a lower sequence which somehow is not yet detected. I guess the other cases are the same. This will sort itself out over time I hope.

[QUOTE=ChristianB;496466]For example: 736584, 880536, 451710, 990582 and others in the 1e6, 2e6 range.[/QUOTE]

292320 <- 736584
40404 <- 880536
258672 <- 451710
46290 <- 990582

2194170 terminates.

[QUOTE=ChristianB;496466]I added this list to the blue page in order to delete the merges but I ended up with new sequences. .
I wonder if this means the list on the blue page is incomplete?[/QUOTE]
No, it doesn't - it simply means that those (in the 2nd column) should be deleted, plain and simple. Nothing needs to be done about the first column.

Example:
If you start a sequence with 1000002, you will get these sequence members
[CODE]Status n Digits Number Checked
0 7 (show) 1000002 = 2 · 3 · 166667 Checked
1 7 (show) 1000014 = 2 · 3 · 166669 Checked
2 7 (show) 1000026 = 2 · 3^4 · 6173 Checked
3 7 (show) 1241136 = 2^4 · 3^3 · 13^2 · 17
[/CODE]Then it doesn't matter that 1000002 merges to anything or not.
1000014 1000026 1241136 should be struck from the list, that's all. - because they are a subsequence of another sequence.

[QUOTE=Batalov;496518]No, it doesn't - it simply means that those (in the 2nd column) should be deleted, plain and simple. Nothing needs to be done about the first column.

Example:
If you start a sequence with 1000002, you will get these sequence members
[CODE]Status n Digits Number Checked
0 7 (show) 1000002 = 2 · 3 · 166667 Checked
1 7 (show) 1000014 = 2 · 3 · 166669 Checked
2 7 (show) 1000026 = 2 · 3^4 · 6173 Checked
3 7 (show) 1241136 = 2^4 · 3^3 · 13^2 · 17
[/CODE]Then it doesn't matter that 1000002 merges to anything or not.
1000014 1000026 1241136 should be struck from the list, that's all. - because they are a subsequence of another sequence.[/QUOTE]

I understand that. What I was worried about is that the numbers in your first column were added to the list while normally they are already on the list. Kar_bon's list fixed that for the examples I posted, since the first column of your list was not the lowest merging sequence for the sequences in the second column. But in order to safely delete sequences from the blue page both seqs must be on the page and the script tests if the higher seq starter merges with the lower seq starter.

2196192 merges with 7044.

2544690 merges with 922158.