Catagolue Oddities

[hth3]

This 2x128 soup is classified as zz_REPLICATOR:

Code: Select all

x = 128, y = 2, rule = B3/S23
bobbbbbooooobbbooobbbobboobobobobbboboobboboobboobbbooooobobbbboboooooooobbobobbobooobobooooboboooboooboobboboobbobobbbbbobbobob$
bbboooboooboboooobbbbbbobobbboboobboobobbobobbbbooobbooboobobboobobobbboobbbooooooooboboobbbbboobbbbboobooobbobobbbboboobooooooo!

Hashsoup link: https://catagolue.hatsya.com/hashsoup/2 ... 8134/b3s23

[confocaloid]

This 2x128 soup is classified as zz_REPLICATOR: [...]

I remember that there were multiple earlier cases of apgsearch classifying something as "zz_...", even if it isn't a growth at all. (Some of those cases are from myself running apgsearch, other cases are from other people.)

Identification is performed automatically, using an imperfect algorithm. AFAIK there is currently no really reliable algorithm for detecting replicators, linear growths, quadratic growths and "explosions" that would work for many different cellular automata. Even writing down definitions is already an open poblem. Even if definitions were written down and well-understood and agreed, it would likely require much more resource usage (computations, memory use) to identify some reactions, more than can be expected from users of the soup searcher program. I think that means there will be further examples of such "apparent misidentifications" (and some of them cannot even be proven to be "misidentifications", simply because there is no consistent, agreed, well-understood definition of what would count as correct identification).

Quoting from the comments section in the page https://catagolue.hatsya.com/object/zz_REPLICATOR/b3s23

On 2024-12-22 at 21:26:07 UTC, nickpoyntz wrote:

B3/S23 occurences: 2x128: None of the 2 soups exhibit any infinite growth??? 8x32: Same here, no infinite growth. D4_x4: Only one soup. It creates 2 switch-engine based puffers which initially have backwards glider streams that I believe confuses whatever identifies patterns. Their ash includes a canoe and boat-tie. D8_1: Most, if not all of these, evolve into puffers with backwards glider streams. Because of the symmetry, these create and destroy bi-blocks repeatedly. D8_4: None of these seem to exhibit infinite growth??

[PK22]

xp14_y1pim0mipzocoa4y34aocoz6c6k8y38k6c6zy16iq0qi6zy11y11 is made up of four tumblers which do not interact, and there are no sample soups shown, but somehow it is listed in the D4_+1 census.

There are two other p14s made up of four non-interacting tumblers, but both have sample soups, and were found by Charity Engine less than four hours apart of each other.

Code: Select all

*** xp14_x8if505fi8z7b80cy1c08b7zed10jy1j01dezx14fa0af41 ***
Soup c_1gfXUpjEIvwx147920269 was found on 2022-02-13 at 10:03:15 UTC and is owned by TechnobladeNeverDies

*** xp14_xgggwj9d0d9jwgggzrraaahy7haaarrzx111wpim0mipw111 ***
Soup c_bEDqzNhjzAbQ53091209 was found on 2022-02-13 at 13:44:32 UTC and is owned by TechnobladeNeverDies

*** xp14_y1pim0mipzocoa4y34aocoz6c6k8y38k6c6zy16iq0qi6zy11y11 ***
There are no sample soups stored in the Catagolue.

Speaking of Charity Engine, do we know why they stopped contributing to Catagolue?

[dvgrn]

Speaking of Charity Engine, do we know why they stopped contributing to Catagolue?

Let's see, I found something from DroneBetter on Discord about that. Let's see if I can dig it up again.

Here it is -- from 4/15/2025:

[diSCOURGEbot#3875]'s owner, @gchromodynamics (not present here) turned it off with the intention of switching both Charity Engine and the Open Science Grid to running their distributed search program, Scourge, but at about the same time problems arose with their permission to use the two projects' resources.

Looks like the big inflection point was around the beginning of September 2024, right?

[Resu]

Glider tagalong gets catagolue confused?
PATHOLOGICAL

Code: Select all

x = 7, y = 6, rule = B3678/S23-a678
bo$2o$obo$4bo$3bo$4bobo!

Example soup :

Code: Select all

x = 16, y = 16, rule = B3678/S23-a678
bbbobbbboboobboo$
obobbbboboobobbb$
bbbobobboooobbbb$
obooobboobbobbbo$
bobobbooobooooob$
ooboobbbobbbooob$
ooobooboobbboboo$
booobooooboboboo$
oobobobbobbooobo$
booobbbobbbobboo$
obbobbbbobbobobb$
ooboobbobbooobob$
obbbooobobobbbob$
boooooooobobbobb$
obbbobbboooboboo$
obobbboooboooooo!

[PK22]

The names for objects (not their apgcodes) have changed, and the wiki links are broken.

[Resu]

Apgserach found some spark-coupled oscillators (only 1 sparker) in alien rules: xp20_4ere4zoozff

[b-engine]

The census of the xq4 in b2i3aciq4cin5e8s01e2aei3i4iq5y contains six distinct non-interacting 2c/4 T-ships. This xq2 is also made out of two non-interacting Ts.

[73times137]

This soup from B3/S23/D8_4 somehow gets classified as PATHOLOGICAL:

Code: Select all

x = 32, y = 32, rule = B3/S23
obobobbbboboobboobboobobbbbobobo$
boboboobbbobooobbooobobbboobobob$
obobboobbbbobboooobbobbbboobbobo$
bobboobobboboobbbboobobboboobbob$
obboobbbooobboobboobbooobbboobbo$
booobbobobboboooooobobbobobbooob$
boobboooooboboobboobobooooobboob$
bbbobboobboobooooooboobboobbobbb$
bbbbooobbbobbobbbbobbobbbooobbbb$
obbbobobboobooobboooboobbobobbbo$
boboobboooobobobboboboooobboobob$
obobbooobbbobbbbbbbbobbbooobbobo$
oobobbbbboobobboobboboobbbbboboo$
bobooooooobbbobbbbobbbooooooobob$
boobooooboobbbbbbbbbboobooooboob$
obobbobobbbbobbbbbbobbbbobobbobo$
obobbobobbbbobbbbbbobbbbobobbobo$
boobooooboobbbbbbbbbboobooooboob$
bobooooooobbbobbbbobbbooooooobob$
oobobbbbboobobboobboboobbbbboboo$
obobbooobbbobbbbbbbbobbbooobbobo$
boboobboooobobobboboboooobboobob$
obbbobobboobooobboooboobbobobbbo$
bbbbooobbbobbobbbbobbobbbooobbbb$
bbbobboobboobooooooboobboobbobbb$
boobboooooboboobboobobooooobboob$
booobbobobboboooooobobbobobbooob$
obboobbbooobboobboobbooobbboobbo$
bobboobobboboobbbboobobboboobbob$
obobboobbbbobboooobbobbbboobbobo$
boboboobbbobooobbooobobbboobobob$
obobobbbboboobboobboobobbbbobobo!

[Chris857]

I think Catagolue is stuck again.

Why do you think so? If it's synthesis jobs, I don't see any failures in the log, and the next job should be in about 30 minutes.

[WhiteHawk]

I think Catagolue is stuck again.

Why do you think so? If it's synthesis jobs, I don't see any failures in the log, and the next job should be in about 30 minutes.

Never mind. I misread the update timing schedule

[Chris857]

Never mind. I misread the update timing schedule

On that note, https://catagolue.hatsya.com/syntheses does currently say "It may take up to 4 hours before your submitted synthesis appears in Catagolue; the update process runs at 00:20, 04:20, 08:20, 12:20, 16:20, and 20:20 UTC each day" - except currently the jobs run every 8 hours instead of every four - in EST, at 7:30am, 3:30pm, and 11:30pm.

[PK22]

x8x4xb357s238investigator/innspectre_stdin_test appears to have only one anonymous contributor who has been uploading to the census for as long as I can remember using Catagolue, and based on the frequency of hauls, they appear to have spent ~658 days total searching, and quite possibly most of those were consecutive. I don't really see why the rule (which is the StateInvestigator for b357s238) is interesting enough to warrant nearly two years of continuous apgsearching (the same CPU time applied to b3s23/C1 could yield around a trillion soups), so I think the most likely explanation is that someone set up some cloud searches and then just forgot about them.

[NNlk05]

xp38_x27y572zx4ey5e4zccoscy5csoccz66376y567366zx4ey5e4zx8sy5s8 contains a pre^4 block so NOT an oscillator
https://imgur.com/a/ZC73F73
linked to in https://catagolue.hatsya.com/census/b3- ... D4_+2/xp38

[LaundryPizza03]

A semi-common object misidentified as having a negative growith rate: yl1716_2_-590_251abdaa7563b151f90502ab87f3ee51/b2ac3acq4ae5is02an3ar4jqrt5c6i. It is a puffer that fires photons backward between two lines of dots and pulls two stable constellations at different speeds.

Code: Select all

x = 16, y = 16, rule = B2ac3acq4ae5i/S02an3ar4jqrt5c6i
o7b2obo2b2o$bobo3bobo5bo$2o2bo4bobobo$3b2obob2o$5ob4ob4o$2o2bobobob3ob
2o$o2b3o2b2o3bo$3bo2bob2ob3obo$2bobo4bo3b3o$b4ob3o$3obo3bob4obo$3o4bo
4bo$4bob5ob2obo$bo4b10o$o2b2ob2obo2bobo$o3b2o2b8o!

[Chris857]

https://catagolue.hatsya.com/census/b3s ... _stdin/xp8 lists xp8_ckg8imge93gz062ao6l495lozw321011 with 2 occurrences in position 42 (as of right now). However, the page for that p8 strangely doesn't list oscthread_stdin as a symmetry it has occurred in.

[SecondTypist]

The number of occurences on the first item of https://catagolue.hatsya.com/census/b3s ... oups/yl288 is linked.

[Chris857]

I don't see that on my end. Any chance your browser is interpreting it as a phone number? If you hover the link, does it have a "tel:" prefix?

[NNlk05]

I don't see that on my end. Any chance your browser is interpreting it as a phone number? If you hover the link, does it have a "tel:" prefix?

That’s the case on my phone.

[squareroot12621]

It seems the annoying telephone links can be removed by adding

Code: Select all

<meta name="format-detection" content="telephone=no">

to the <head> of the webpage.

[NNlk05]

Somehow this is a ov_q4:

Code: Select all

x = 16, y = 16, rule = B3/S23-a5
3o2bobobobo3bo$2ob4ob3o3bo$obobobo3bob4o$o3b7o2bobo$3b2o2b5obobo$3b2o
4b2ob2o$2obob2o6b3o$3bobob2obob4o$4o3bo2b2obo$2bobo2bo2bo3bo$5o3bob2o
b2o$obo3bo2b2obo2bo$ob3o3bo2b3o$3b3obob2obo2bo$3obob3obo2b3o$b2o5b4ob
o!

Maybe because of the overlapping lanes?