Page 30 of 34
Re: Catagolue Oddities
Posted: November 11th, 2022, 7:00 am
by apg
GUYTU6J wrote: November 11th, 2022, 2:14 am
2. When updating synthesis,
jobs log like this mentions a lengthy list of apgcodes mysteriously, saying "435 apgcodes with better syntheses in Catagolue: ..." What does it mean?
That means that Catagolue has syntheses that are better than Shinjuku + contrib.sjk. These are either invalid apgcodes (such as the xq96 at the beginning, which should really be removed from synthesis-costs) or objects where the synthesis components have been removed from Shinjuku (usually by Parcly Taxel).
Re: Catagolue Oddities
Posted: November 11th, 2022, 8:01 am
by hotdogPi
GUYTU6J wrote: November 11th, 2022, 2:14 am
3. Check the xp264 entry on Syntheses. Why is the name "period-sextupled period-44 pi-heptomino hassler" assigned to a trivial p264 (I see it being p88 on one side and p132 on the other) rather than a nontrivial p264?
This one is my fault when I added a whole bunch of names. It was supposed to go to the other one that was nontrivial.
Re: Catagolue Oddities
Posted: December 1st, 2022, 4:41 am
by GUYTU6J
This step of glider synthesis
was submitted twice and no error was indicated in the job logs, and the
starting constellation has a synthesis, but for now there is no complete synthesis displayed for the target
xp120_y064koy1ca23zycoge2zykgggzy6ew96y4hhhzwccyg111zgggyg66z0hhhy4ciwez111zy38e13zy6o8a6y1354c.
Code: Select all
x = 50, y = 35, rule = B3/S23
2bo44bo$obo42b2o$b2o43b2o2$29bo5bo$29b2o3b2o$22b2o5b2o3b2o$22b2o6bo3bo
$b2o$2bo$2bobo$3b2o38bo$41b3o$40bo$40b2o6b2o$48bo$46bobo$2b2o42b2o$bob
o$bo$2o6b2o$9bo$6b3o$6bo38b2o$45bobo$47bo$47b2o$15bo3bo6b2o$14b2o3b2o
5b2o$14b2o3b2o$14bo5bo2$2b2o43b2o$3b2o42bobo$2bo44bo!
Re: Catagolue Oddities
Posted: December 1st, 2022, 10:48 am
by apg
Thanks for noticing that! This may actually be the oddest Catagolue oddity ever, so congratulations. It turns out that the synthesis has been in Catagolue this whole time, just on completely the wrong page (!!!):
https://catagolue.hatsya.com/object/xq9 ... 5553/b3s23
The reason for this problem was that the always_include string at the top of diffupdate.py was as follows:
Code: Select all
# RLE syntheses for linear-growth patterns (update these, but be careful
# that they're absolutely correct before committing because there are no
# validity checks):
always_include = '''
#CSYNTH yl78_1_20_ce2bb2c697ad330277935c32ef179035 costs 14 gliders (true).
x = 74, y = 80, rule = B3/S23
66bobo$66b2o$67bo14$39bo11bobo$39bobo9b2o$39b2o11bo3$54b3o$54bo$55bo7$
51bo$49b2o$50b2o4$23bo$24bo$22b3o46b3o$bo69bo$2bo69bo$3o46b3o$49bo$50b
o4$22b2o$23b2o$22bo7$18bo$19bo$17b3o3$21bo11b2o$21b2o9bobo$20bobo11bo
14$6bo$6b2o$5bobo!
#CSYNTH yl1344_2_1118_c2aaaf958f8f412c06554ab3e40b8749 costs 6 gliders (true).
x = 23, y = 23, rule = B3/S23
9bobo$10b2o$10bo6bo$16bo$16b3o$20b2o$20bobo$20bo2$o$b2o$2o5$3b2o$2bob
o$4bo2$5b3o$5bo$6bo!
#CSYNTH yl46_1_10_ace82e6a60e972a3a224b998d5e29b17 costs 10 gliders (true).
x = 82, y = 47, rule = B3/S23
59bobo$59b2o$60bo3$obo$b2o$bo11$47bobo$48b2o$48bo$32b2o$27bo4bobo18bob
o$27b2o3bo16bo3b2o$26bobo18bobo4bo$48b2o$33bo$32b2o$32bobo11$80bo$79b
2o$79bobo3$21bo$21b2o$20bobo!
#CSYNTH xq96_y933zy1oozzg8oya4aa4z707y3ggymgoz69992k8w1221yl101z07ycgzybs01h5o80oc8coykggzyg1y1gg8ugicyf11x444ozym1o0h8ym8hzyo1yn121zyoo772ywko8zyo1zytgggcecy0g84w8ep9azyzy111w23y0hvazyzya4k680ogybo4ozyzyb44401yd1yboozyzyo696zyzyl4i48gyb66zyzyi22203443w55553 costs 0 gliders.
'''
When diffupdate.py uploads syntheses from Shinjuku to Catagolue, it prepends this always_include string to the beginning of the payload.
Now, Catagolue uses the exclamation mark at the end of a non-comment line to mark the end of a pattern. But this particular non-synthesis (which was added to remove the xq96 from the tabulation, because it's the wrong (non-canonical) apgcode for that Cordership) doesn't end in an exclamation mark, so Catagolue continues reading until it hits the next exclamation mark -- which is the end of the
next pattern, i.e. the first pattern in the list of apgcodes to update. That's why the glider synthesis ends up having two headers:
Code: Select all
#C [[ GRID MAXGRIDSIZE 14 THEME Catagolue ]]
#CSYNTH xq96_y933zy1oozzg8oya4aa4z707y3ggymgoz69992k8w1221yl101z07ycgzybs01h5o80oc8coykggzyg1y1gg8ugicyf11x444ozym1o0h8ym8hzyo1yn121zyoo772ywko8zyo1zytgggcecy0g84w8ep9azyzy111w23y0hvazyzya4k680ogybo4ozyzyb44401yd1yboozyzyo696zyzyl4i48gyb66zyzyi22203443w55553 costs 0 gliders.
#CSYNTH xp120_y064koy1ca23zycoge2zykgggzy6ew96y4hhhzwccyg111zgggyg66z0hhhy4ciwez111zy38e13zy6o8a6y1354c costs 36 gliders (true).
#CLL state-numbering golly
x = 333, y = 54, rule = B3/S23
237bo$189bo45bobo4bo$190b2o44b2o5b2o13bo63bo$189b2o51b2o12b3o51bo
9b3o$255bo54b3o6bo$255b2o56bo5b2o$187b2o52bo70b2o$186bobo52b2o2b3o
$132b2o54bo6b2o43bobo4bo12b2o62b2o$73bo58bo62bo50bo13bo63bo$72bo
57bobo60bobo62bobo61bobo$65bo6b3o55b2o61b2o63b2o62b2o$64b2o$64bobo
$57b3o$59bo271bo$58bo17bo61b3o60b3o62b3o46bobo11bo2bo$76bobo58b3o
60b3o62b3o48b2o3bo7bo2bo$76b2o238bo4bobo6bo$71b3o70bo176b2o$71bo
63bo7bo186bo$72bo60bobo7b3o31bo22b3o62b3o61bo2bo$134b2o42bo22b3o
62b3o60bo2bo$139b3o34b3o152bo$139bo104b2o62b2o$140bo57bo45b2o62b2o
$181b3o15bo$181bo15b3o$114bo67bo82b2o62b2o$115bo149b2o62b2o$113b3o
86b3o102bo$119b2o56b3o22bo39b3o61bo2bo$44bo64b3o7bobo56b3o22bo39b
3o60bo2bo$45bo65bo7bo188bo$43b3o64bo205b2o$39b2o267bo6bobo4bo$38bo
bo74b3o60b3o62b3o60bo2bo7bo3b2o$40bo73b3o60b3o62b3o61bo2bo11bobo$
6bo300bo$5bo$5b3o$obo$b2o39b3o9b2o67b2o61b2o63b2o62b2o$bo42bo8bobo
66bobo60bobo62bobo61bobo$43bo9bo68bo62bo64bo13bo49bo$52b2o67b2o61b
2o6bo56b2o12bo4bobo42b2o$192bobo68b3o2b2o$192b2o75bo55b2o$254b2o
62b2o5bo$255bo63bo6b3o$190b2o60b3o12b2o47b3o9bo$189b2o61bo13b2o5b
2o41bo$191bo76bo4bobo$273bo!
This problem has been in there for ages, but it's gone unnoticed because the apgcodes are uploaded in lexicographic order, and therefore usually the pattern that gets swallowed up is the pentadecathlon (xp15_4r4z4r4) that's automatically included every time for testing purposes. It's only apgcodes that precede xp15_4r4z4r4 in lexicographical order that could be affected by this bug, and moreover the bug only manifests when there's a single batch (i.e. <= 800 apgcodes) being uploaded by the job (only the last batch in the job has the always_include RLEs prepended to it).
Re: Catagolue Oddities
Posted: December 13th, 2022, 2:09 am
by LaundryPizza03
Even though INT B0 is not supported yet, the rule
b01e3s23 has an empty census.
Re: Catagolue Oddities
Posted: December 24th, 2022, 4:47 pm
by muzik
I'm not sure why pattern categories aren't shown here:
https://catagolue.hatsya.com/census/b2- ... 34567c8/C1
Re: Catagolue Oddities
Posted: December 28th, 2022, 6:05 am
by bibunsekibun
In the latest haul of B34j5y/S23, PATHOLOGICAL is displayed as occurring 2 times, but it actually occurred 4 times.
EDIT: Shouldn't yl32_1_288_a2945b4c0b9b2f46ad3ba2e7b48154c3 be yl128 instead of yl32?
Re: Catagolue Oddities
Posted: January 28th, 2023, 8:40 pm
by Chris857
https://catagolue.hatsya.com/object/xp2 ... 16a4/b3s23 has the name "spark coil on diagnal_boats". Biggest problem is the misspelling of "diagonal", but also why an underscore?
Re: Catagolue Oddities
Posted: February 1st, 2023, 6:57 pm
by Apersoma
The only census for the rule Iceballs contains only period 5 oscillators. This is especially weird considering how basic & common some photons are in that rule. Also there is a p2 oscillator with just 2 cells that should be able to be picked-up by any census unless it was only looking for p5 oscillators.
https://catagolue.hatsya.com/census/b25 ... 8/iii1x256
Re: Catagolue Oddities
Posted: February 1st, 2023, 7:06 pm
by hotdogPi
Apersoma wrote: February 1st, 2023, 6:57 pm
The only census for the rule Iceballs contains only period 5 oscillators. This is especially weird considering how basic & common some photons are in that rule. Also there is a p2 oscillator with just 2 cells that should be able to be picked-up by any census unless it was only looking for p5 oscillators.
https://catagolue.hatsya.com/census/b25 ... 8/iii1x256
This is a 3× (i.e. 2^3) inflated symmetry, which means each "cell" is actually an 8×8 square.
Re: Catagolue Oddities
Posted: February 2nd, 2023, 11:10 am
by Apersoma
Oh, I didn't know that. Also what do mean by that the cells are 3x3 squares? How does it work when only part of the square is on but part of it isn't.
Re: Catagolue Oddities
Posted: February 2nd, 2023, 11:22 am
by hotdogPi
Apersoma wrote: February 2nd, 2023, 11:10 am
Oh, I didn't know that. Also what do mean by that the cells are 3x3 squares? How does it work when only part of the square is on but part of it isn't.
Only the initial configuration has squares like that. It evolves normally.
Example:
Code: Select all
x = 8, y = 8, rule = B3/S23
4b2o$4b2o$2b6o$2b6o$2b2o2b2o$2b2o2b2o$4o$4o!
Re: Catagolue Oddities
Posted: February 2nd, 2023, 11:28 am
by Apersoma
That makes a lot more sense now. Ty!
Re: Catagolue Oddities
Posted: February 23rd, 2023, 7:52 pm
by pipsqueek
why is there an extra queen bee in gun_3000,
Code: Select all
x = 78, y = 63, rule = B3/S23
14b2o$5bo8b2o$4bo5bo6b2o52b2o$4bob2o3bo5b3o5b2o44b2o$5b6o6b2o6b2o$6b4o
4b2o$14b2o2$2b2obob2o2$2bo5bo$26bobo$3b2ob2o16bo3bo40b2obob2o$5bo18bo
19bo$17b2o4bo4bo14b4o22bo5bo$17b2o5bo12bo4b2obobo$24bo3bo3bob2o5b3obo
2bo2b2o17b2ob2o$26bobo2bob4o5b2obobo3b2o19bo$31b2o2b2o6b4o17b2o$9b2o
33bo19bo$2b3o50b2o5bobo$bo3bo47bo2bo5b2o$40bobo9bo$o5bo33bo3bo7bo14b2o
$2o3b2o17bobo17bo7bo20b3o$24b2o4b2o8bo4bo7bo2bo15bo3bo$25bo4b2o12bo10b
2o$3bo36bo3bo26bo5bo$2bobo35bobo8bobo17b2o3b2o$2bobo47b2o$2bo11b3o9bo
25bo$2bo11bo2bo7bo4b2o42bo$2bo2bo9bo8b2o4b2o41bobo$3b2o68bobo$10b2obo
2bo34bo9b3o11bo$10bo5bo6bo2bo3b3o13b2o4bo7bo2bo11bo$11bo3bo8bo6b2o13b
2o4b2o8bo9bo2bo$12b3o13b2o43b2o$18b3o7b3o10bo19bo2bob2o$29bobo7b3o3b3o
3bo2bo6bo5bo$30b2o6bo6b2o6bo8bo3bo$38b2o8b2o13b3o$47b3o7b3o$46bobo$46b
2o$4b2o$5bo$2b3o$2bo$27b2o43b2o$26bobo43bo$26bo46b3o$25b2o48bo7$36b2o$
35bobo8bo$35bo11bo$34b2o9b3o!
when it could just be replaced with a block?
Code: Select all
x = 78, y = 65, rule = B3/S23
5b2o$5b2o3$71b2o$71b2o5$2b2obob2o2$2bo5bo$26bobo$3b2ob2o16bo3bo40b2obo
b2o$5bo18bo19bo$17b2o4bo4bo14b4o22bo5bo$17b2o5bo12bo4b2obobo$24bo3bo3b
ob2o5b3obo2bo2b2o17b2ob2o$26bobo2bob4o5b2obobo3b2o19bo$31b2o2b2o6b4o
17b2o$9b2o33bo19bo$2b3o50b2o5bobo$bo3bo47bo2bo5b2o$40bobo9bo$o5bo33bo
3bo7bo14b2o$2o3b2o17bobo17bo7bo20b3o$24b2o4b2o8bo4bo7bo2bo15bo3bo$25bo
4b2o12bo10b2o$3bo36bo3bo26bo5bo$2bobo35bobo8bobo17b2o3b2o$2bobo47b2o$
2bo11b3o9bo25bo$2bo11bo2bo7bo4b2o42bo$2bo2bo9bo8b2o4b2o41bobo$3b2o68bo
bo$10b2obo2bo34bo9b3o11bo$10bo5bo6bo2bo3b3o13b2o4bo7bo2bo11bo$11bo3bo
8bo6b2o13b2o4b2o8bo9bo2bo$12b3o13b2o43b2o$18b3o7b3o10bo19bo2bob2o$29bo
bo7b3o3b3o3bo2bo6bo5bo$30b2o6bo6b2o6bo8bo3bo$38b2o8b2o13b3o$47b3o7b3o$
46bobo$46b2o$4b2o$5bo$2b3o$2bo$27b2o43b2o$26bobo43bo$26bo46b3o$25b2o
48bo7$36b2o$35bobo8bo$35bo11bo$34b2o9b3o!
Re: Catagolue Oddities
Posted: February 23rd, 2023, 9:16 pm
by dvgrn
pipsqueek wrote: February 23rd, 2023, 7:52 pm
why is there an extra queen bee in gun_3000,
when it could just be replaced with a block?
The extra queen bee makes the bounding box smaller.
The rules are arbitrary, but those are the rules: any Rube Goldbergian awkward extra addition is okay, as long as it reduces the bounding box.
Re: Catagolue Oddities
Posted: March 4th, 2023, 2:31 am
by confocaloid
It seems like the "readsynth" queue is not fully emptied when an update job arrives. If I understand correctly, one RLE always remains in the "readsynth" queue, and is reprocessed again in subsequent update jobs, until there are new RLEs in the queue. This leads to multiple occurrences of a given RLE in different logs.
For example, the following fragment appears in the log for
jobs/3874168633:
Code: Select all
x = 0, y = 0, rule = B3/S23
158$171.A$170.A$170.3A5$159.A.A$159.2A$160.A2$154.2A8.3A$155.2A7.A$154.A10.A3$150.A$150.2A$149.A.A!
# Filtering with radius 5
# Engulfing 456zy74oczy22a6y346azyhc68
# processing src=xs0_0, dst=xs18_wcid1egoz311...
# ...success.
# Filtering with radius 8
# Filtering with radius 13
# Filtering with radius 21
6207 original contributions
b'Valid password.\nOperation successful.\n'
Saved contributions into shinjuku/comp/cached_contrib.sjk
Deleting 11 RLEs...
The operation completed successfully.
and the following fragment appears in the next update log,
jobs/3874547473:
Code: Select all
x = 0, y = 0, rule = B3/S23
158$171.A$170.A$170.3A5$159.A.A$159.2A$160.A2$154.2A8.3A$155.2A7.A$154.A10.A3$150.A$150.2A$149.A.A!
# Filtering with radius 5
# Engulfing 456zy74oczy22a6y346azyhc68
# processing src=xs0_0, dst=xs18_wcid1egoz311...
# ...success.
# Filtering with radius 8
# Filtering with radius 13
# Filtering with radius 21
6207 original contributions
Note that the processed RLE is the same in both fragments, i.e. it is re-processed again. As of the time I'm posting this, the following is the contents of the "readsynth" queue:
Code: Select all
x = 0, y = 0, rule = B3/S23
158$171.A$170.A$170.3A5$159.A.A$159.2A$160.A2$154.2A8.3A$155.2A7.A$154.A10.A3$150.A$150.2A$149.A.A!
Re: Catagolue Oddities
Posted: March 4th, 2023, 10:31 pm
by dvgrn
confocaloid wrote: March 4th, 2023, 2:31 am
It seems like the "readsynth" queue is not fully emptied when an update job arrives.
I believe this is an accurate summary of the current rather mysterious behavior. I've never heard an explanation that really explained the design reasons behind this, though Adam did discuss it briefly
on Discord in 2019:
calcyman wrote:The /readsynth queue always leaves behind exactly one RLE -- because, you know, the empty set.
[ Heav — 05/29/2019 2:35 PM: @apgoucher name one bad thing about the empty set ]
It neither has an epsilon-minimal element, nor does it have a choice function. The axioms of foundation and choice literally have to be written to explicitly say 'every non-empty set'.
I'd really rather the readsynth queue were able to be empty when it's actually empty. My preferred workaround to any empty-set problems would be to always append the same recipe to the readsynth queue before attempting to do anything with it -- a standard "hacker emblem" 1G synthesis of a glider, let's say.
Re: Catagolue Oddities
Posted: March 25th, 2023, 5:07 pm
by Ian07
The
Sir Robin page gives the following error:
Code: Select all
Request failed: Unexpected exception from servlet: java.lang.ArrayIndexOutOfBoundsException: Index 1 out of bounds for length 1
It appears to be related to the NFT section, as
doo-dah's page is also broken.
Re: Catagolue Oddities
Posted: March 25th, 2023, 8:28 pm
by confocaloid
Sometimes the error message is shorter:
Code: Select all
Request failed: Unexpected exception from servlet: java.lang.ArrayIndexOutOfBoundsException
Re: Catagolue Oddities
Posted: May 1st, 2023, 2:24 am
by confocaloid
Edit: the synthesis was posted on the forum:
viewtopic.php?p=164563#p164563
(May be already known, probably needs human intervention)
Someone else submitted a synthesis for
a p183 oscillator. The submission was processed in
j4203816384, but incompletely. For instance this step was not accepted:
Code: Select all
#C From synthesis in https://gitlab.com/hatsya/open-source/catagolue/-/jobs/4203816384
#C src=xp3_mtexo8g0ggznsoy0qb8fgkcz121y11178czzzzzzyh6ak8wcik8, dst=xp3_257631136752zx6a8c0s4ozy0311d961156zyzy4ggcimggox66zyzy5347062aczyzy5oo
x = 48, y = 66, rule = B3/S23
36bo$bo34bobo$2bo12bobo18b2o$3o13b2o$16bo$38b3o$38bo$39bo2$33bo$31b2o$
32b2o4$23bo4bo$21b2o4b2o$22b2o3bobo4$17b2o4bo$16bo2bo2bobo$17bobo3bobo
$18bo5b2o28$34b2o$34bobo$36bo8bo$36b3o5bobo$34b2o3bo3bo2bo$33bo2b4o$
33b2obo7bobo$36bob2o6b2o$36bobo7b2o$35b2obobo3bobo$39b2o$43bo2bo$44bob
o$45bo!
I tried resubmitting that single step in a separate RLE, but
that did not work.
I checked that the complete synthesis is valid, by creating a 89G continuous version.
Re: Catagolue Oddities
Posted: May 26th, 2023, 7:11 am
by Anivec
xp420_vtvz757zac4zzzzzzzzzzzzyzy6vtvzyzy6757 seems to have the wrong synthesis. The synthesis has 3 pentadecathlons instead of 2.
EDIT:
never mind, it just has two steps instead of one
Re: Catagolue Oddities
Posted: July 9th, 2023, 4:04 am
by Chris857
70P26 shows a 37G synth with a pair of 10G steps to get to
an intermediate pseudo still life. But that particular still life clearly has an 18G synth. Why hasn't the 70P26 synth updated itself?
Edit: I resubmitted the whole synth and it seems to have sorted itself out.
Re: Catagolue Oddities
Posted: July 13th, 2023, 9:48 pm
by carsoncheng
In an attempt to reduce the
p55 pre-pulsar hassler synthesis, I have submitted these two components:
Code: Select all
x = 0, y = 0, rule = B3/S23
8bo$9b2o$8b2o4$34bo$33bobo$34bo$11bo$12bo10b2o7b5o$10b3o11bo7bo4bo$23b
o11bo2bo$23b2o2b2o6b2obo2bo$26bobo3bo5bobobo$23b2obo4bobo4bo2bo$23b2o
b2o3bo2bo2b2o$32b2o7$10b3o$12bo$11bo4$35bo$7b3o23bo2bo$9bo23bo2bo$bo6b
o25bo$b2o$obo2$32b2o$23b2ob2o3bo2bo2b2o$23b2obo4bobo4bo2bo$26bobo3bo5b
obobo$23b2o2b2o6b2obo2bo$23bo11bo2bo$24bo7bo4bo$23b2o7b5o2$34bo$33bob
o$34bo!
Code: Select all
x = 0, y = 0, rule = B3/S23
34bo$33bobo$34bo2$23b2o7b5o$24bo7bo4bo$23bo11bo2bo$23b2o2b2o6b2obo2bo$
26bobo3bo5bobobo$23b2obo4bobo4bo2bo$22bobob2o3bo2bo2b2o$23bo8b2o2$obo$
b2o$bo6bo$9bo$7b3o5$11bo$12bo$10b3o22bo$33bo2bo$33bo2bo$34bo4$32b2o$
23b2ob2o3bo2bo2b2o$23b2obo4bobo4bo2bo$26bobo3bo5bobobo$23b2o2b2o6b2obo
2bo$23bo11bo2bo$10b3o11bo7bo4bo$12bo10b2o7b5o$11bo$34bo$33bobo$34bo4$
8b2o$9b2o$8bo!
For some reason, both components were not processed correctly (even though they are valid); the log mentions that they are "null components". Here is the
job log from line 145 to 181 (the lines logging the processing of these two components):
Code: Select all
x = 0, y = 0, rule = B3/S23
8bo$9b2o$8b2o4$34bo$33bobo$34bo$11bo$12bo10b2o7b5o$10b3o11bo7bo4bo$23b
o11bo2bo$23b2o2b2o6b2obo2bo$26bobo3bo5bobobo$23b2obo4bobo4bo2bo$23b2o
b2o3bo2bo2b2o$32b2o7$10b3o$12bo$11bo4$35bo$7b3o23bo2bo$9bo23bo2bo$bo6b
o25bo$b2o$obo2$32b2o$23b2ob2o3bo2bo2b2o$23b2obo4bobo4bo2bo$26bobo3bo5b
obobo$23b2o2b2o6b2obo2bo$23bo11bo2bo$24bo7bo4bo$23b2o7b5o2$34bo$33bob
o$34bo!
# Filtering with radius 5
# Engulfing yfgiligzyeg9g0641u08k8zye122hg011zyfrq2pg8ozzzwg8oy0217y8712y2ocgzy01z532
# processing src=xs48_0giligzg9g0641u08k8z122hg011z0rq2pg8o, dst=xs49_2lmg6246z0hg23z3421o81v04a4z03iai21zx1...
# ...success.
# Engulfing y0321j8brzy0gg01h88gz2520fg4c01i1x2994zy219l91
# Null component
# Filtering with radius 8
# Filtering with radius 13
# Engulfing y2giligyhgiligz8k80u1460g9gx8ii4y8g9g0641u08k8zy0110gh221yf122hg011zy0o8gp2qryhrq2pg8ozzzybg8oy0217y8712y2ocgzyd1zy9532
# processing src=xp2_y0321j8bryhrb8j123zy0gg01h88gyfg88h10ggz2520fg4c01i1y07ey91i10c4gf0252zy219l91yh19l91, dst=xp2_y06426gml2ygmmg6246zy332ghyhhg23z4a40v18o1243y9sey03421o81v04a4zy112iai3yh3iai21zy41yl1...
# ...success.
# Filtering with radius 21
x = 0, y = 0, rule = B3/S23
34bo$33bobo$34bo2$23b2o7b5o$24bo7bo4bo$23bo11bo2bo$23b2o2b2o6b2obo2bo$
26bobo3bo5bobobo$23b2obo4bobo4bo2bo$22bobob2o3bo2bo2b2o$23bo8b2o2$obo$
b2o$bo6bo$9bo$7b3o5$11bo$12bo$10b3o22bo$33bo2bo$33bo2bo$34bo4$32b2o$
23b2ob2o3bo2bo2b2o$23b2obo4bobo4bo2bo$26bobo3bo5bobobo$23b2o2b2o6b2obo
2bo$23bo11bo2bo$10b3o11bo7bo4bo$12bo10b2o7b5o$11bo$34bo$33bobo$34bo4$
8b2o$9b2o$8bo!
# Filtering with radius 5
# Engulfing yfgiligzy74ii8xg9g0641u08k8zye122hg011zyfrq2pg8ozzzwg8oy0217y8712y2ocgzy01z532
# processing src=xp2_y0321j8brzy0gg01h88gz2520fg4c01i1y07ezy219l91, dst=xp2_y06426gml2zy332ghz4a40v18o1243y0eszy112iai3zy41...
# ...success.
# Engulfing 2lmg6246z0hg23z3421o81v04a4z03iai21zx1
# Null component
# Filtering with radius 8
# Filtering with radius 13
# Engulfing y2giligyhgiligz8k80u1460g9gy84ii8xg9g0641u08k8zy0110gh221yf122hg011zy0o8gp2qbgygrq2pg8ozy61zzybg8oy0217y8712y2ocgzyd1zy9532
# processing src=xp2_y06426gml2ygmmg6246zy332ghyhhg23z4a40v18o1243y9sey03421o81v04a4zy112iai3yh3iai21zy41yl1, dst=xp2_y06426gml2yf2lmg6246zy332ghyhhg23z4a40v18o1243y0esy93421o81v04a4zy112iai3yh3iai21zy41yl1...
# ...success.
Re: Catagolue Oddities
Posted: July 16th, 2023, 4:42 pm
by Chris857
This p52 is showing something weird on the synth viewer - leftmost edge there is a XWSS just sailing off to the left never to interact with anything.
Re: Catagolue Oddities
Posted: July 16th, 2023, 11:00 pm
by Ian07
Chris857 wrote: July 16th, 2023, 4:42 pm
This p52 is showing something weird on the synth viewer - leftmost edge there is a XWSS just sailing off to the left never to interact with anything.
Looks like the MWSS is actually step 1 of the synthesis. You'll see in step 2 that it starts out fully formed right from generation 0, while everything else in that step is just gliders, so technically it's a MWSS-to-xs18_8kidik8zw343 component. Probably some sort of mistake involving someone forgetting to advance the middle five gliders to make the
xs14_4a9mkk8zx1. Had they done so, the step would've been interpreted as starting out with the xs14 and converting it into the xs18 using 6 gliders and an MWSS, the latter of which would've automatically been converted to its 3G recipe.
This does, however, raise another question, as the synthesis for
xs18_8kidik8zw343 itself doesn't contain this error, despite it being an intermediate step to the xp52.
carsoncheng wrote: July 13th, 2023, 9:48 pm
In an attempt to reduce the
p55 pre-pulsar hassler synthesis, I have submitted these two components:
For some reason, both components were not processed correctly (even though they are valid); the log mentions that they are "null components". Here is the
job log from line 145 to 181 (the lines logging the processing of these two components):
Haven't fully figured out this one either (other than submitting an issue to Gitlab, which I have
just done) but what I
can say is that the "null components" are simply due to the update script initially only looking within a 5-cell radius to connect disparate regions to each other as a single component.
Code: Select all
# Filtering with radius 5
# Engulfing yfgiligzyeg9g0641u08k8zye122hg011zyfrq2pg8ozzzwg8oy0217y8712y2ocgzy01z532
# processing src=xs48_0giligzg9g0641u08k8z122hg011z0rq2pg8o, dst=xs49_2lmg6246z0hg23z3421o81v04a4z03iai21zx1...
# ...success.
# Engulfing y0321j8brzy0gg01h88gz2520fg4c01i1x2994zy219l91
# Null component
The first engulfed region here,
xp0_yfgiligzyeg9g0641u08k8zye122hg011zyfrq2pg8ozzzwg8oy0217y8712y2ocgzy01z532, is a valid 5G component, albeit not the one intended. It consists of the gliders colliding with just the top half of the constellation. As for the bottom half, that gets engulfed as
xp0_y0321j8brzy0gg01h88gz2520fg4c01i1x2994zy219l91, which does not contain any gliders/xWSSes and so is in fact a null component.
Once the radius is increased, however, the job log seems to indicate that the synths
were processed correctly:
Code: Select all
# Filtering with radius 13
# Engulfing y2giligyhgiligz8k80u1460g9gx8ii4y8g9g0641u08k8zy0110gh221yf122hg011zy0o8gp2qryhrq2pg8ozzzybg8oy0217y8712y2ocgzyd1zy9532
# processing src=xp2_y0321j8bryhrb8j123zy0gg01h88gyfg88h10ggz2520fg4c01i1y07ey91i10c4gf0252zy219l91yh19l91, dst=xp2_y06426gml2ygmmg6246zy332ghyhhg23z4a40v18o1243y9sey03421o81v04a4zy112iai3yh3iai21zy41yl1...
# ...success.
is the correct 5G component, and the source and destination are both correct. Yet despite the source having a 73G synthesis listed, no updates appear to have been made to the synthesis database as a result of this, and the destination is still 82G. No clue why.