Suggested LifeWiki edits

For discussion directly related to LifeWiki.
User avatar
LaundryPizza03
Posts: 2298
Joined: December 15th, 2017, 12:05 am
Location: Unidentified location "https://en.wikipedia.org/wiki/Texas"

Re: Suggested LifeWiki edits

Post by LaundryPizza03 » May 21st, 2022, 3:43 pm

At Lake,the following passage:

Code: Select all

Larger lakes with complex outlines may be contracted several times, e.g. the 5th lake listed above yields 16 different semilakes.
should be changed to:

Code: Select all

Larger lakes with complex outlines may be contracted several times, e.g. the 6th lake listed above yields 16 different semilakes.

Code: Select all

x = 4, y = 3, rule = B3-q4z5y/S234k5j
2b2o$b2o$2o!
LaundryPizza03 at Wikipedia

User avatar
77551enpassant
Posts: 46
Joined: February 18th, 2022, 9:06 pm
Location: Portland, Oregon

Re: Suggested LifeWiki edits

Post by 77551enpassant » May 21st, 2022, 5:33 pm

Done.
I enjoy self-supporting spaceships

Code: Select all

x = 11, y = 14, rule = B3/S23
2bo$3b2o$obo$o9$10bo$9b2o!
#C[[ THEME Golly GRID ]]

User avatar
wwei47
Posts: 1651
Joined: February 18th, 2021, 11:18 am

Re: Suggested LifeWiki edits

Post by wwei47 » May 21st, 2022, 7:22 pm

There does exist a P1 superstring in HighLife.

Code: Select all

x = 16, y = 4, rule = B36/S23:T16,0
16o$bobobobobobobobo$obobobobobobobo$obobobobobobobo!
Help me find high-period c/2 technology!
My guide: https://bit.ly/3uJtzu9
My c/2 tech collection: https://bit.ly/3qUJg0u
Overview of periods: https://bit.ly/3LwE0I5
Most wanted periods: 76,116

dani
Posts: 1222
Joined: October 27th, 2017, 3:43 pm

Re: Suggested LifeWiki edits

Post by dani » May 21st, 2022, 8:54 pm

Something I think could be beneficial is to either expand glossary of basic terms or make a more thorough glossary page. Updating the Life Lexicon seems to be a much slower process and it's not entirely complete for newer terminology like "index fossil" (a term for an object that appears twice or more naturally from the same basic seed)

The wiki seems like the perfect medium for a more up-to-date, community driven glossary.

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Suggested LifeWiki edits

Post by confocaloid » May 21st, 2022, 9:31 pm

Currently 1G seed and 1 glider seed are redirects to "Seed" which describes one-glider seeds. OTOH the page Beehive contains sentence "There are also formations of two beehives that also occur fairly commonly, evolving from seeds known as butterfly and teardrop." The latter two linked pages also seem to use "seed" with meaning "predecessor". Should links "seed" be replaced with "predecessor" as appropriate, and/or the page "Seed" expanded to cover a different meaning of the word (as used e.g. in Conway's Game of Life)?
127:1 B3/S234c User:Confocal/R (isotropic rules, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » May 21st, 2022, 11:17 pm

confocaloid wrote:
May 21st, 2022, 9:31 pm
Currently 1G seed and 1 glider seed are redirects to "Seed" which describes one-glider seeds. OTOH the page Beehive contains sentence "There are also formations of two beehives that also occur fairly commonly, evolving from seeds known as butterfly and teardrop." The latter two linked pages also seem to use "seed" with meaning "predecessor". Should links "seed" be replaced with "predecessor" as appropriate, and/or the page "Seed" expanded to cover a different meaning of the word (as used e.g. in Conway's Game of Life)?
I liked the second option, so I added a sentence about the less technical use of "seed" to mean basically "initial configuration" -- which is definitely a related usage, but without the connotation of "stationary constellation being hit by something signal-like".

Book
Posts: 385
Joined: August 28th, 2021, 2:38 pm
Location: California
Contact:

Re: Suggested LifeWiki edits

Post by Book » May 22nd, 2022, 3:00 pm

There are but two remaining articles tagged as having questionable notability. Both are now marked for deletion.
Phil Bookman

User avatar
rowett
Moderator
Posts: 3777
Joined: January 31st, 2013, 2:34 am
Location: UK
Contact:

Re: Suggested LifeWiki edits

Post by rowett » May 24th, 2022, 3:19 am

I ran a script to validate the rules in the Rule namespace on LifeWiki. The following rules have issues. Please let me know if they need fixing or can be deleted.

Missing @RULE: Errors:
  • Error reading Rules/1-2-10symbiosis.table on line 4: var b={1,2,3,4,5,6,7,8,9,10} - state value out of range
  • Error reading Rules/1-2-Brick10.table on line 4: var a={0,1,2,3,4,5,6,7,8,9,10} - state value out of range
  • Error reading Rules/10Symbiosis.table on line 4: var b={1,2,3,4,5,6,7,8,9,10} - state value out of range
  • Error reading Rules/LifeNonHistory.table on line 40: cc,6,i,j,k,l,m,n,o,0
  • Error reading Rules/Warringtwolife.table on line 4: var aa = (0,2,3)
  • Error reading Rules/WartimeLifeLife.table on line 4: var aa = (0,2,3)
Also are LifeHistory and LifeSuper still needed now they are natively supported by Golly and LifeViewer? Perhaps for other tools.

dani
Posts: 1222
Joined: October 27th, 2017, 3:43 pm

Re: Suggested LifeWiki edits

Post by dani » May 24th, 2022, 4:21 am

I think it's good to have those last two ruletables there anyway for archival's sake.

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » May 24th, 2022, 8:29 am

dani wrote:
May 24th, 2022, 4:21 am
I think it's good to have those last two ruletables there anyway for archival's sake.
Yeah, I use them sometimes as a starting point for making new rules -- better to leave them where they are, as long as they don't cause any trouble.

Book
Posts: 385
Joined: August 28th, 2021, 2:38 pm
Location: California
Contact:

Re: Suggested LifeWiki edits

Post by Book » May 24th, 2022, 2:28 pm

Can we get admin help untangling the Lobster net (https://conwaylife.com/wiki/Talk:Lobster_(spaceship))?
Phil Bookman

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » May 24th, 2022, 9:30 pm

Book wrote:
May 24th, 2022, 2:28 pm
Can we get admin help untangling the Lobster net (https://conwaylife.com/wiki/Talk:Lobster_(spaceship))?
Done, according to suggestions found on the Lobster (spaceship) talk page (two article deletions to prepare for moving Lobster_(spaceship) to Lobster. Let me know if I didn't do it right...

Chris857
Posts: 252
Joined: June 10th, 2020, 11:26 pm

Re: Suggested LifeWiki edits

Post by Chris857 » May 26th, 2022, 12:27 am

New SKOP102, need updating at https://conwaylife.com/wiki/Oscillator and https://conwaylife.com/wiki/Unix (where mentioning the unix loop is probably still fine, but not SKOP any more).

Edit: and https://conwaylife.com/wiki/Table_of_os ... _by_period links to a p102 (two Beluchenko's p51 hassling beehive) that isn't even the p102 unix loop.

GUYTU6J
Posts: 2200
Joined: August 5th, 2016, 10:27 am
Location: 拆哪!I repeat, CHINA! (a.k.a. 种花家)
Contact:

Re: Suggested LifeWiki edits

Post by GUYTU6J » May 30th, 2022, 5:54 am

In 2011, Nathaniel deleted 48P22, a page created by Sokwe sometime ago. But in 2016, Apple Bottom created a 48P22.1 page. I would like to have the deleted page be restored to see if they are the same oscillator. (If yes, that would be an interesting case to indicate that the notability criteria has been changing over the years.)
Furthermore, if confirmed, a history move/merge and redirect creation needs to be done like for muzik's Honey factory. As we have a proposal for discarding ".1", the article name should be chosen as 48P22.

User avatar
Ian07
Moderator
Posts: 891
Joined: September 22nd, 2018, 8:48 am
Location: New Jersey, US

Re: Suggested LifeWiki edits

Post by Ian07 » May 30th, 2022, 11:34 am

GUYTU6J wrote:
May 30th, 2022, 5:54 am
In 2011, Nathaniel deleted 48P22, a page created by Sokwe sometime ago. But in 2016, Apple Bottom created a 48P22.1 page. I would like to have the deleted page be restored to see if they are the same oscillator.
Unfortunately, the undeletion page doesn't show any history for 48P22, other than the fact that it was deleted. As far as I can tell, there's nothing left to restore.

Chris857
Posts: 252
Joined: June 10th, 2020, 11:26 pm

Re: Suggested LifeWiki edits

Post by Chris857 » June 1st, 2022, 9:55 am

https://conwaylife.com/wiki/Toad/Snippet (today's featured article) says "It is the second most common naturally-occurring oscillator, being less common than beacon..."

I think this is supposed to say "being more common than beacon" since beacon is the third most common.

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » June 1st, 2022, 11:34 am

Chris857 wrote:
June 1st, 2022, 9:55 am
https://conwaylife.com/wiki/Toad/Snippet (today's featured article) says "It is the second most common naturally-occurring oscillator, being less common than beacon..."

I think this is supposed to say "being more common than beacon" since beacon is the third most common.
Fixed (I think!). Thanks for the report!

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Suggested LifeWiki edits

Post by confocaloid » June 2nd, 2022, 2:29 pm

The article Periodic currently begins with text "Periodic can refer to two different concepts." My edit which added links Stable conduit and Periodic conduit was partially reverted with edit summary "Just link to stable or periodic instead of adding a "conduit" in the link".

Question: Is it appropriate to have less specific links to pages describing multiple different meanings, or rather more specific links to dedicated articles and/or appropriate redirects? I think that in cases like this one, more specific links are better, because they imply less about the structure of the rest of LifeWiki.
127:1 B3/S234c User:Confocal/R (isotropic rules, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.

GUYTU6J
Posts: 2200
Joined: August 5th, 2016, 10:27 am
Location: 拆哪!I repeat, CHINA! (a.k.a. 种花家)
Contact:

Re: Suggested LifeWiki edits

Post by GUYTU6J » June 5th, 2022, 9:52 pm

confocaloid wrote:
June 2nd, 2022, 2:29 pm
The article Periodic currently begins with text "Periodic can refer to two different concepts." My edit which added links Stable conduit and Periodic conduit was partially reverted with edit summary "Just link to stable or periodic instead of adding a "conduit" in the link".

Question: Is it appropriate to have less specific links to pages describing multiple different meanings, or rather more specific links to dedicated articles and/or appropriate redirects? I think that in cases like this one, more specific links are better, because they imply less about the structure of the rest of LifeWiki.
My intention is to reduce the number of redirect pages, which take up space on the server. But I have decided to tolerate that move.

But then...
In [https://conwaylife.com/w/index.php?title=R64&curid=11636&diff=108917&oldid=108621 this edit summary] you wrote:After thinking about it, linking stable conduit still seems to be better than stable conduit, more or less for the same reason as glider eater seems to be better than glider eater
(Wiki syntax translated into BBCode)
Now this is in danger of setting off an explosion of redirects: if there is "glider eater" as a whole, would a "LWSS eater" be needed? How about "lightweight spaceship eater"? "MWSS eater", "HWSS eater", "Loafer eater", or even "2-engine Cordership eater'? So I have to say no to this case.

What is bad about implying more about the structure of the rest of LifeWiki? Isn't it an editor's duty to check out relevant concepts and carefully avoid unnecessary red links?

User avatar
confocaloid
Posts: 2729
Joined: February 8th, 2022, 3:15 pm

Re: Suggested LifeWiki edits

Post by confocaloid » June 5th, 2022, 10:11 pm

GUYTU6J wrote:
June 5th, 2022, 9:52 pm
Now this is in danger of setting off an explosion of redirects: if there is "glider eater" as a whole, would a "LWSS eater" be needed? How about "lightweight spaceship eater"? "MWSS eater", "HWSS eater", "Loafer eater", or even "2-engine Cordership eater'? So I have to say no to this case.
How likely it is that someone later will come later after me and write a good article "Glider eater"?
How likely it is that someone later will come later after me and write a good article "Loafer eater"?
How likely it is that someone later will come later after me and write a good article "Sir Robin eater"?
I believe asking yourself these questions and answering them may help to make decisions of this kind in each specific case.
GUYTU6J wrote:
June 5th, 2022, 9:52 pm
My intention is to reduce the number of redirect pages, which take up space on the server. But I have decided to tolerate that move.

But then...
In [https://conwaylife.com/w/index.php?title=R64&curid=11636&diff=108917&oldid=108621 this edit summary] you wrote:After thinking about it, linking stable conduit still seems to be better than stable conduit, more or less for the same reason as glider eater seems to be better than glider eater
(Wiki syntax translated into BBCode)
Now this is in danger of setting off an explosion of redirects: if there is "glider eater" as a whole, would a "LWSS eater" be needed? How about "lightweight spaceship eater"? "MWSS eater", "HWSS eater", "Loafer eater", or even "2-engine Cordership eater'? So I have to say no to this case.

What is bad about implying more about the structure of the rest of LifeWiki? Isn't it an editor's duty to check out relevant concepts and carefully avoid unnecessary red links?
1) Edit history also takes up space, including articles and talk pages. So by that logic, after all it might be reasonable to move discussion of LifeWiki issues to the forum to avoid cluttering the wiki history (?)
2) It is much easier to check out relevant concepts when there are tools to do that. One such tool is "What links here".
3) The less implications between different pages, the easier it is to maintain the wiki.

PS: And please remember people here are volunteers. They have different backgrounds, different knowledge, there are some very smart and skillful people here - but they are volunteers. So please no talk about "duty". Probably you can expect people to read your questions but you cannot demand answers from them.
127:1 B3/S234c User:Confocal/R (isotropic rules, incomplete)
Unlikely events happen.
My silence does not imply agreement, nor indifference. If I disagreed with something in the past, then please do not construe my silence as something that could change that.

User avatar
pzq_alex
Posts: 792
Joined: May 1st, 2021, 9:00 pm
Location: tell me if you know

Re: Suggested LifeWiki edits

Post by pzq_alex » June 5th, 2022, 10:51 pm

GUYTU6J wrote:
June 5th, 2022, 9:52 pm
But then...
In [https://conwaylife.com/w/index.php?title=R64&curid=11636&diff=108917&oldid=108621 this edit summary] you wrote:After thinking about it, linking stable conduit still seems to be better than stable conduit, more or less for the same reason as glider eater seems to be better than glider eater
(Wiki syntax translated into BBCode)
Now this is in danger of setting off an explosion of redirects: if there is "glider eater" as a whole, would a "LWSS eater" be needed? How about "lightweight spaceship eater"? "MWSS eater", "HWSS eater", "Loafer eater", or even "2-engine Cordership eater'? So I have to say no to this case.

What is bad about implying more about the structure of the rest of LifeWiki? Isn't it an editor's duty to check out relevant concepts and carefully avoid unnecessary red links?
IMO, in this case, it is better to format the text as “glider eater”, “LWSS eater”, etc., as any reader coming across this link will know what a glider/LWSS is. It also doesn’t seem noteworthy to create separate pages called “glider eater”, “LWSS eater” (see LW:NB).
\sum_{n=1}^\infty H_n/n^2 = \zeta(3)

How much of current CA technology can I redevelop "on a desert island"?

carsoncheng
Posts: 471
Joined: June 11th, 2022, 11:24 pm

Re: Suggested LifeWiki edits

Post by carsoncheng » June 12th, 2022, 1:56 am

These are the outdated syntheses on LifeWiki. They have already been submitted to Catagolue.

Code: Select all

x = 935, y = 321, rule = B3/S23
62$119bobo$119b2o$120bo24$100bobo44bobo$101b2o44b2o202bo$101bo46bo201b
2o$345bobo2bobo$346b2o210bo$279bo66bo75bo136bo$97bo4b2o100bo75b2o74b3o
61bobo134b3o231bo35bobo$97b2o2bobo101bo73b2o22bo52bo64b2o368bobo34b2o
$96bobo4bo99b3o3bo92bo54bo129bo127bo44bo130b2o35bo$208b2o92b3o121bo61b
2o124bobo42bobo65bo$208bobo215bobo58b2o126bo44b2o65bobo$426b2o69bo118b
o43b2o65b2o3bobo94b2o$495b2o119bo44b2o69b2o96b2o62bo$205b2o222bo66b2o
115bo3bo40bo3bo70bo95bo4b2o4b2o50bobo$204bobo222bobo69b2o110b4o41b4o172b
obo2bobo51b2o$206bo222b2o69b2o274bo59bo2bo60bo8bobo$116b2o171bo206b2o
4bo110b2o43b2o63bo50bobo59bo2bo59bo9b2o$115bobo4bo166bobo148b3o52b2o116b
2o43b2o63bobo49b2o60b2o60b3o8bo$117bo3b2o166b2o134b3o12bo56bo82b3o68b
obo69b2o$121bobo303bo13bo138bo71b2o135bo$221b2o54b3o4b3o139bo67bo86bo
70bo9bo125bo108b2o$116bo103b2o57bo6bo84b2o120b2o160b3o3b2o125b3o4b2o100b
obo3bo$116b2o104bo55bo6bo84b2o121bobo122b2o37bo3bobo130b2o101bo4bo$115b
obo233b2o19bo203b3o38bo2bo35bo61bobo3bo71bo105b3o$350bobo223bo41b2o99b
2o3bobo58b2o$352bo219b2o3bo36b2o103bo4b2o58bobo$566b2o3bobo39bobo170b
o$364bo202b2o4bo41bo$363b2o201bo$363bobo4$83bo$83b2o$82bobo4bo$89b2o$
88bobo73$694bo$694bobo$694b2o4$267bo417bo$267bobo413bobo$267b2o415b2o
2$357bo332bo$268b2o88bo325bobo3bobo$87bo13bobo163b2o87b3o326b2o3b2o$87b
obo6bo4b2o166bo415bo28bo$87b2o7bobo3bo599bobo5bo2bo$96b2o604b2o4b2o3b
3o$73bobo185bo6b3o270bobo159bo5b2o$74b2o13b2o168b2o7bo225bo47b2o140bo
$74bo13b2o170b2o7bo222b2o48bo22bo53bobo63b2o2bobo$90bo402b2o70bobo52b
2o62b2o3b2o11b2o$134b2o10b2o106bo167bo45bo96b2o53bo69bo10b2o6b3o125bo
$134bobob2o6b2o61bo45b2o165bobo44bo17bo207b2o6bo5bo84bo42bobo$82b2o15b
2o35bobobo66bobo44b2o166b2o43b3o15b2o208b2o13bo72bo10bobo40b2o$83b2o13b
2o36bobo10b2o57b2o3bo103bo54bo7bo105b2o296b2o8b2o32bo$82bo17bo33bobob
ob2o7bobo60bo89bo12bobo54bobo4bo39b2o132b2o164b3o61b2o44bo$134b2o2bo10b
o62b3o88bo10bo4bo52b2o5b3o37b2o131bobo116bo19b2o6b2o18bo69bo37b3o3b4o
$77bo60b2o161b3o10b6o96bo137bo71b3o43bo18b2o6b2o19bo66b2o43bob2obo$77b
2o293b2o38bo2bobo65b3o142bo3bo37b3o115b2o2b2o38b2o2b2o$76bobo226b2o7b
4o53bobo38b4obo67bo70bo70bo3b2o159bobo37b2o2b2o$245b3o57b2o7bo2bo55bo
42bo67bo70b2o74bobo47bo13b2o95bo39bob2obo$414bo140bobo124bo5bo6b2o136b
4o3b3o$414b2o264b3o6b2o10bo138bo$366b2o320b2o11b2o3b2o83bo49bo$365bob
o108b2o222bobo2b2o83b2o39b2o$322bo44bo107bobo229bo82bobo37bobo$322bob
o152bo82b3o118b2o5bo143bo$322b2o236bo77b2o36b3o3b2o4b2o$561bo75b2o39b
o2bo5bobo$319bo319bo37bo28bo$318bobo379b2o3b2o$318bobo378bobo3bobo$319b
o381bo2$706b2o$706bobo$706bo4$696b2o$695bobo$697bo!
50P92.1 (cheapest variant): 12G ➡️ 10G
Bipole : 5G ➡️ 4G (it was mentioned on the forums before, but was somehow forgotten)
Bookend bridge house: 6G ➡️ 5G
Bun bridge bun: 8G ➡️ 6G
Bun with feather: 6G ➡️ 5G
Carrier siamese hook with tail: 7G ➡️ 5G; Carrier siamese hook-with-tail tail ➡️ Carrier siamese hook-with-tail
Cis-boat up on candlefrobra: 10G ➡️ 9G
Cis-snake on bookend: 6G ➡️ 5G
Claw test tube baby: 8G ➡️ 7G
Fore and back: 6G ➡️ 5G
Griddle and dock: 12G ➡️ 9G
Griddle and table: 10G ➡️ 9G
Hexagonal key: 7G ➡️ 6G
Shift-bookend and bun: 6G ➡️ 5G
Snake siamese long snake: 6G ➡️ 5G
Statorless p6: 29G ➡️ 28G (it was mentioned on the article, but the synthesis cost in the infobox was never updated)
Super pond: 10G ➡️ 9G
Cis-bipole_on_table: 8G ➡️ 7G

Edit: "Cis-bipole on table" was added to the list.
Last edited by carsoncheng on June 12th, 2022, 6:40 am, edited 1 time in total.

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » June 12th, 2022, 2:59 am

carsoncheng wrote:
June 12th, 2022, 1:56 am
These are the outdated syntheses on LifeWiki. They have already been submitted to Catagolue.
I've gone ahead and updated all these numbers in the relevant articles.

How did you determine this list? There's a rather clunky script that I wrote, that I usually re-run to do several types of sanity check including this, a few times per year. Looks like it has been a while since the last run, if the most recent checked-in report is any indication (and it certainly should be).

If you'll create a LifeWiki account with the same name as your forum account and get the trusted flag set (it's an easy process, more or less a formality, only necessary to keep spammers out) then you're welcome to make these kinds of changes yourself. It's usually easier to do your own editing than to spend the time carefully writing up lists of changes for other people to make.

carsoncheng
Posts: 471
Joined: June 11th, 2022, 11:24 pm

Re: Suggested LifeWiki edits

Post by carsoncheng » June 12th, 2022, 3:03 am

The code is here:

Code: Select all

print("This program is for checking whether the synthesis cost of LifeWiki is up-to-date. Preparing lookup...")
import requests
print("Looking for patterns. Please wait...")
list_of_urls = []
current_url_old = requests.get("https://conwaylife.com/w/index.php?title=Category:Patterns").text
while True:
    try:
        current_url = current_url_old.split("total.")[1].split("</div></div></div>")[0]
    except IndexError:
        pass
    for item in current_url.split("\n"):
        try:
            link = item.split('href="')[1].split('"')[0]
            title = link.split("/")[-1]
            list_of_urls.append("https://conwaylife.com/w/index.php?title=" + title + "&action=edit")
        except IndexError:
            pass
    if "next page" in current_url_old and "(next page)" not in current_url_old:
        link = current_url_old.split("pagefrom")[1].split('"')[0]
        newlink = "https://conwaylife.com/w/index.php?title=Category:Patterns&pagefrom" + link
        current_url_old = requests.get(newlink).text
    else:
        print("Lookup complete. Starting next section...")
        break
for item in list_of_urls:
    try:
        info = requests.get(item).text
        text = info.split('wpTextbox1">')[1].split("</textarea>")[0]
        if "synthesis" in text and "apgcode" in text:
            apgcode = (text.split("apgcode")[1].split("=")[1].split("\n")[0])[1:]
            cost = int(text.split("synthesis")[1].split("=")[1].split("\n")[0])
            synth_info = requests.get("https://catagolue.hatsya.com/textsamples/" + apgcode + "/b3s23/synthesis").text
            if "costs" in synth_info:
                glider_cost = int(synth_info.split("costs ")[1].split(" gliders")[0])
                if glider_cost < cost:
                    print(item + "\nThis object has a cheaper synthesis.")
            if "synthesis2" in text and "apgcode2" in text:
                apgcode = (text.split("apgcode2")[1].split("=")[1].split("\n")[0])[1:]
                cost = int(text.split("synthesis2")[1].split("=")[1].split("\n")[0])
                synth_info = requests.get("https://catagolue.hatsya.com/textsamples/" + apgcode + "/b3s23/synthesis").text
                if "costs" in synth_info:
                    glider_cost = int(synth_info.split("costs ")[1].split(" gliders")[0])
                    if glider_cost < cost:
                        print(item + "\nThis object has a cheaper alternate synthesis.")
    except:
        pass
It does not have an auto-upload function. Instead, it points out the pages that need to be updated.

Also, should we consider making a LifeWiki template for the synthesis costs to be updated dynamically without manual edits?

User avatar
dvgrn
Moderator
Posts: 10612
Joined: May 17th, 2009, 11:00 pm
Location: Madison, WI
Contact:

Re: Suggested LifeWiki edits

Post by dvgrn » June 12th, 2022, 3:28 am

carsoncheng wrote:
June 12th, 2022, 3:03 am
Also, should we consider making a LifeWiki template for the synthesis costs to be updated dynamically without manual edits?
That would certainly be nice, if someone wants to take the time to figure out how to do it.

On the other hand, the number of changes needed per year along these lines has been gradually decreasing, so this hasn't been a particularly high-priority to solve.

Also, I have a vague memory of it being difficult to set up a template to retrieve this information from a non-conwaylife.com location. Maybe it would require regularly updating some suitably reduced copy of a "textcensus" file? In which case, it seems almost just as easy for everyone to simply keep updating individual synth numbers whenever they notice a discrepancy.

Post Reply