[QUOTE=EdH;596289]Is anyone working base 70 or 71?[/QUOTE]I'm going to start working on the table for base 70. The following exponents are already initialized by :anonymous: (unless someone else takes credit):[code]1, 2, 4, 6, 8, 10, 12, 13, 14, 16, 18, 19, 20, 22, 24, 26, 28[/code]70^3 should be credited to Paul Zimmerman, since he has it reserved in the main project, via a merge with 1134.

Thank you very much Edwin.
Keep us posted and let me know when I can add the 70 and 71 bases.

Otherwise, we can also see that yafu stats are still higher than normal right now.
Progress is faster...

[QUOTE=garambois;596324]Thank you very much Edwin.
Keep us posted and let me know when I can add the 70 and 71 bases.

Otherwise, we can also see that yafu stats are still higher than normal right now.
Progress is faster...[/QUOTE]I won't start 71 for some time. If someone else wants it in the meantime, just go ahead, and let me know. I'll post here when I do move to it.

Base 73 table is completely initialized (1-100), with all matched parities terminated and all unmatched either terminated or paused with a composite cofactor >99 dd.

Moving to base 70. . .

I forgot to run merge checks on base 73, but there was only one:[code]73^46:i1430 merges with 11820:i43[/code]However, the interesting find is that in base 70, there is another matched parity open end sequence:[code]70^3:i33 merges with 1134:i9
70^9:i3869 merges with 56910:i27
70^15:i370 merges with 1488:i7
[B]70^72:i85 merges with 1074:i2[/B][/code]The turn upward resulted from hitting 55^2 at iteration 84.

[QUOTE=EdH;596514]I forgot to run merge checks on base 73, but there was only one:[code]73^46:i1430 merges with 11820:i43[/code]However, the interesting find is that in base 70, there is another matched parity open end sequence:[code]70^3:i33 merges with 1134:i9
70^9:i3869 merges with 56910:i27
70^15:i370 merges with 1488:i7
[B]70^72:i85 merges with 1074:i2[/B][/code]The turn upward resulted from hitting 55^2 at iteration 84.[/QUOTE]


Thank you Edwin for all this work.
Yes, we rarely find this phenomenon of matched parity open end sequence.
The phenomenon had already occurred for example for 29^15 or 47^97.
I hope to have an update for the next weekend.

Page updated.
Many thanks to all for your help !

[B]Added base : 73.[/B]
[B]Still no non-trivial end of sequence for bases 276, 552.[/B]

Our project now has 113 bases and 10362 sequences.

@Edwin : For the "initialization" of the base 73, I don't know how you managed to finish all the calculations for all the matched parities sequences in such a short time ?
This requires a large amount of calculations since some of these sequences started with more than 180 digits !
This is a remarkable feat !
;-)

[QUOTE=garambois;596910]. . .
@Edwin : For the "initialization" of the base 73, I don't know how you managed to finish all the calculations for all the matched parities sequences in such a short time ?
This requires a large amount of calculations since some of these sequences started with more than 180 digits !
This is a remarkable feat !
;-)[/QUOTE]I do have a few machines, but I think I was quite lucky with larger exponents for base 73. I don't seem to be doing near as well with base 70.

Two alternate notes:

- I will be starting on some of the smaller exponents for base 71 sometime soon.

- If anyone keeps a local set of all the sequence .elfs for all the tables, let me know if there is interest in a pair of scripts that I use to keep my local set updated. It surprises me how many sequences have been advanced, every time I run the scripts.

I'm going to start working on the table for base 71. The following exponents are already initialized by :anonymous: (unless someone else takes credit):[code]1, 2, 3, 4, 5, 6, 7, 9, 11, 13, 15, 17, 19, 21, 23, 25, 27, 29, 31, 37, 41, 43, 61, 71[/code]
71^8 should be credited to Walter Krickau, since he has it reserved in the main project, via a merge with 1578.

I've been working on 385^4 via a merge with 903872, so please reserve this one for me.

Until now, I had never noted the reservations for the sequences in our project that merge with those in the main project and are reserved in the main project.
I just specified on the page that there is a merger with a sequence of the main project.
And in that case, you have to refer to the blue page to see who the sequence is reserved for in the main project.
If I note down these reservations, I have to check each time I update our project that the sequences of the main project are still reserved by the same person.
Indeed, I think that there are many people who work for the main project and not for our project and who would not inform me here of their abandonment of reservation for the sequences of the main project which concern us.
So I don't think it's efficient for us to start noting some of the merged sequence reservations and not others.

Are you sure that I should just note some reservations for sequences that merge with the main project and not others ?