ConwayLife.com

danny wrote:I always found that weird since 'tubebaby' isn't a word...

I previously wrote:Potentially the common names mapping could be automatically updated from the object pages on LifeWiki, if there's an API to download this data?

$ curl http://conwaylife.com/wiki/Pond_on_dock?action=edit 2>/dev/null | grep '^|.*='
|name             = Pond on dock
|pname            = pondanddock
|c                = 18
|bx               = 8
|by               = 6
|rulemin          = B/S23
|rulemax          = B3678/S012345678
|rulespecial      = [[Conway's Game of Life|Conway Life]]
|rle              = true
|apgcode          = xs18_3lk453z3443
|niemiecid        = 18.2387
|pentadecathlonid = 18.2654
|viewerconfig     = #C [[ GPS 2 THUMBSIZE 2 ]]

calcyman wrote:

I previously wrote:Potentially the common names mapping could be automatically updated from the object pages on LifeWiki, if there's an API to download this data?

I've figured out how to do this from the command-line using curl:

Code: Select all

$ curl http://conwaylife.com/wiki/Pond_on_dock?action=edit 2>/dev/null | grep '^|.*='
|name             = Pond on dock
|pname            = pondanddock
|c                = 18
|bx               = 8
|by               = 6
|rulemin          = B/S23
|rulemax          = B3678/S012345678
|rulespecial      = [[Conway's Game of Life|Conway Life]]
|rle              = true
|apgcode          = xs18_3lk453z3443
|niemiecid        = 18.2387
|pentadecathlonid = 18.2654
|viewerconfig     = #C [[ GPS 2 THUMBSIZE 2 ]]

Would anyone (@Nathaniel, @AppleBottom, @dvgrn) be vehemently opposed to me running over a thousand GET requests to LifeWiki to obtain a more comprehensive 'common names' list for use in Catagolue?

One appealing aspect is that the 'common names' list could also store auxiliary information, including links from the Catagolue object pages back to the LifeWiki.

calcyman wrote:One appealing aspect is that the 'common names' list could also store auxiliary information, including links from the Catagolue object pages back to the LifeWiki.

muzik wrote:Currently we're trying to reach a consensus on the wiki for pattern naming, which might take a while, so that we can have a cleaner, more consistent methodology for systematically naming still lifes and oscillators, which should eventually carry on to Catagolue. (You're welcome to join in by the way.)

calcyman wrote:I decided to do this anyway. Take a look at xs12, for instance: ...

calcyman wrote:Would anyone (@Nathaniel, @AppleBottom, @dvgrn) be vehemently opposed to me running over a thousand GET requests to LifeWiki to obtain a more comprehensive 'common names' list for use in Catagolue?

77topaz wrote:I just noticed an enormous pile of submitted but unverified/uncommitted hauls sitting in the b3s23/C1 census backlog. The weird thing is that, despite this backlog, apgsearch's /verify function claims there are no more hauls to verify. What's up with that?

77topaz wrote:The strange thing is that my apgsearch keeps saying "No more hauls to verify." even when there are clearly still many hauls in the "?committed=0" log. This didn't happen, for example, when rliston was submitting many b3s23/C1 hauls quickly; those just verified normally and that backlog was eventually cleared when I edited my apgsearch to essentially work as a full-time verification script. But this approach isn't working for me now, because apgsearch isn't even recognising that this backlog of hauls needs to be verified.

• Hauls received from apgsearch immediately have committed=0;
• The cron process moves them to either committed=1 (if verification is enabled) or commits them immediately (if verification is disabled);
• Instances of apgsearch verify hauls in the committed=1 group, moving them to either committed=3 (successful) or committed=4 (unsuccessful);
• If verification is enabled, the cron process commits anything with committed=3 (moving them to committed=2).

77topaz wrote:EDIT: The transcluded-information-from-Fano boxes for outer-totalistic rules seem to have disappeared.

77topaz wrote:For range-1 Generations rules, a LifeViewer is rendered if the pattern has no state-2+ cells in its canonical phase (example), but only a static image is shown otherwise (example). It's a bit weird, because both of these examples are in the same rule and both have a functional apgcode, yet one has a LifeViewer and one does not.