OK, page updated.
Thanks a lot to all for your help !

:smile:

I think 31^36 may have merged.

[QUOTE=RichD;558264]I think 31^36 may have merged.[/QUOTE]
I don't show any merge, but that should not be considered conclusive. . .

[QUOTE=RichD;558264]I think 31^36 may have merged.[/QUOTE]


If there was a merge of 31^36, then it is not with a sequence from the main project.
It must be with another sequence whose last 80 digits term is not on my page : [URL]http://www.aliquotes.com/OE_3000000_C80.txt[/URL]
I don't know how to find this merge ?

[QUOTE=garambois;558275]If there was a merge of 31^36, then it is not with a sequence from the main project.[/QUOTE]

At index 1924, that term was added to FDB by me today.
At index 1925 (and forward), that composite was added Nov 4, 2018.
A quick snapshot is at: [url]http://factordb.com/sequences.php?se=1&aq=31%5E36&action=range&fr=1922&to=1930[/url]

Unfortunately, I don't know how to determine which sequence was merged with if it's not with a sequence from the main project !
I don't even know how you were able to determine when the old sequence was entered ?

[QUOTE=RichD;558277]At index 1924, that term was added to FDB by me today.
At index 1925 (and forward), that composite was added Nov 4, 2018.
A quick snapshot is at: [url]http://factordb.com/sequences.php?se=1&aq=31%5E36&action=range&fr=1922&to=1930[/url][/QUOTE]

Numbers 18 digits and smaller are preloaded into the database (hence why they match their own ID numbers rather than having sequentially assigned ones in the 1100.... range), so that's probably the last date the database was refreshed.

[QUOTE=garambois;558333]Unfortunately, I don't know how to determine which sequence was merged with if it's not with a sequence from the main project !
I don't even know how you were able to determine when the old sequence was entered ?[/QUOTE]

Click on the composite in question, say the one at index 1924. A new page will be displayed. Click the little green arrow after More information. It shows a Create Time of Sep 29, 2020. Repeat the process for index 1925. In fact the last composite at index 3829 shows a Create Time of Dec 15, 2019.

Edit: The next to last number, a C102 at index 3828, was added on Nov 4, 2018. It took over a year to advance one term - whatever sequence this is. :smile:

[QUOTE=RichD;558343]Edit: The next to last number, a C102 at index 3828, was added on Nov 4, 2018. [/QUOTE]

[QUOTE=factordb]Before November 4, 2018, 12:20 am[/QUOTE]
All numbers with Nov 4 date is a lie. It just means the database was rebuilt on that date and they lost all history of any existing numbers. Hence the "before"

[QUOTE=axn;558347]All numbers with Nov 4 date is a lie. It just means the database was rebuilt on that date and they lost all history of any existing numbers. Hence the "before"[/QUOTE]

Ah, OK. The point is "that sequence" was known before I started working on 31^36 this week. It found (merged with?) an existing sequence and suddenly advanced nearly 2000 terms. I was simply stating what I thought the merge point might be.

[QUOTE=RichD;558343]Click on the composite in question, say the one at index 1924. A new page will be displayed. Click the little green arrow after More information. It shows a Create Time of Sep 29, 2020. Repeat the process for index 1925. In fact the last composite at index 3829 shows a Create Time of Dec 15, 2019.

Edit: The next to last number, a C102 at index 3828, was added on Nov 4, 2018. It took over a year to advance one term - whatever sequence this is. :smile:[/QUOTE]


Thank you very much, I didn't know that such information could be found on factordb !!!