Apgsearch issue in B3-k5cj6a7/S2n3-k4-jnry5-cjn6ce7e8

[LaundryPizza03]

Hi, apgluxe 4.72 seems to have chickened out in the rule B3-k5cj6a7/S2n3-k4-jnry5-cjn6ce7e8, thanks to this small c/137o spaceship from the 5s database:

Code: Select all

x = 8, y = 3, rule = B3-k5cj6a7/S2n3-k4-jnry5-cjn6ce7e8
2o$3o2b3o$2o!

It persistently reports a failure to detect periodic behavior at an unprecedented rate.

[77topaz]

This is hardly the first rule to behave like this. Omosso (B2k3acijr4ijqy6i7c/S2aek3ijnqr4it5n) is another example - and, not coincidentally, it's also a rule with small but very slow spaceships. The point is that this warning doesn't really matter when it occurs this frequently (it merely means the soups are being rule for longer than "usual" because they stabilise more slowly) - apgsearch will still search the rule. Rules that actually freeze apgsearch won't show anything on the console, because explosions will prevent the script from even reaching the threshold for the extension warning message.

Also, in future, I'd suggest posting these kinds of messages in one of the existing apgsearch/Catagolue-related threads, instead of creating a new thread for each one.

[dani]

Can confirm this happened at one point with B35j7e/S23, with its R pentomino ship.

[LaundryPizza03]

I can confirm that this still happens in v5.09-ll2.2.12, in the rule B3aijqr4cjrt5acy6an/S1c2-c3-acy4acer5ack6en7e. This rule has a 5-cell 2c/352o spaceship:

Code: Select all

x = 4, y = 2, rule = B3aijqr4cjrt5acy6an/S1c2-c3-acy4acer5ack6en7e
o2bo$3o!