Moosey wrote:Similarly:
Code: Select all
#C stolen from Catagolue
x = 42, y = 43, rule = B3/S23
4bobo$5b2o$5bo4$9bo$7bobo$8b2o3$11bo$9bobo$10b2o5$o13bo20b2o$b2o11bobo
17bo2bo$2o12b2o17bob2obo$34bo2bo$35b2o18$39b3o$39bo$40bo!
How do I get this to the wiki?
After searching the wiki for a RLE:honeycomb_synth under the everything (I.e. capable of searching user, RLE, etc. Namespaces) , I found no helpful page.
The general idea would be to go ahead and create the
RLE:honeycomb_synth page, and add text like this to it:
Code: Select all
#C 6-glider synthesis of honeycomb
x = 42, y = 43, rule = B3/S23
4bobo$5b2o$5bo4$9bo$7bobo$8b2o3$11bo$9bobo$10b2o5$o13bo20b2o$b2o11bobo
17bo2bo$2o12b2o17bob2obo$34bo2bo$35b2o18$39b3o$39bo$40bo!
This is a weird case, as you've discovered, because an outdated pattern file was already uploaded to the server, and only moderators and admins can go in and manually delete files off the server. I've done that now. That means that a newly created RLE:honeycomb_synth will now be picked up by the auto-upload script. The script will automatically generate the
#N honeycomb_synth.rle and
#C http://conwaylife.com/wiki/Honeycomb lines.
... Just FYI for anyone else reading this who wants to know how this stuff works: the old file looked like this --
Code: Select all
#N honeycomb_synth.rle
#O Chris Cain, 24 November 2014
#C 9-glider synthesis of honeycomb
#C http://conwaylife.com/wiki/Honeycomb
#C http://conwaylife.com/forums/viewtopic.php?p=14496#p14496
x = 44, y = 34, rule = B3/S23
26bo$26bobo$26b2o5$24bo$24bobo$24b2o$17bobo$17b2o$18bo2$2bo6bo30b2o$ob
o4bobo29bo2bo$b2o5b2o28bob2obo$16bo22bo2bo$14b2o24b2o$15b2o2$27b2o$27b
obo$27bo7$21b2o$7b2o12bobo$8b2o11bo$7bo!
The auto-upload script is very conservative, so it never automatically overwrites an already uploaded pattern file with anything it finds in the RLE namespace.
Maybe A Report Will Help
Eventually I'm planning to add a reporting feature to the auto-upload script so that it makes a folder showing RLE-namespace patterns vs. LifeWiki server patterns for any cases where there are patterns in both places and they don't match.
It might be a good while before that happens, though, because I'm not sure I really
want to fight all the way through a report like that and fix everything that shows up.
Here's What I Think About Uploading Syntheses, But This Is Just Me
As mentioned
elsewhere, neither Catagolue's nor Mark Niemiec's or Heinrich Koenig's current synthesis databases are up to date at the moment. We really need a single "source of truth" database that anyone can update, but we don't have that yet. Until the
new edition of Mark's database becomes available, I'm hoping nobody will start any Grand Projects of adding lots of new RLE:{pname}_synth files by just copying blindly from Catagolue or anywhere else.
It seems fine to add any synthesis that you're sure is the latest greatest up-to-datest -- if enough people do that, then the LifeWiki will eventually become our "source of truth" database. It's just not such a good idea to copy syntheses en masse from any existing database; that's potentially a huge waste of time (in my opinion, anyway) because it will add lots of syntheses that just have to be deleted again.
Forlorn Hopes For Future Vaporware
Really I hope that we eventually won't have to upload any _synth files at all. Ideally the LifeWiki should just link directly to a hypothetical separate "source of truth" glider synthesis database -- preferably one that accepts crowdsourced contributions of new syntheses, checks to make sure they're valid, and immediately makes them available.
The closest thing we have to that right now is the RLE namespace. Theoretically a script could be written to check new RLE:{pname}_synth files, and immediately complain about any that aren't new records, or that don't actually construct the object they promise to construct. But to do that we'd need to have a way to mark a single synthesis as the record holder. Current _synth files often include lots of different ways of building something, or they include both an incremental and a continuous synthesis, or they're in Mark Niemiec's multistate format instead of plain RLE, or they're only uploaded to the server and not available in the RLE namespace at all... etc., etc.