Eureka
Eureka (or p30 pre-pulsar shuttle) is a period-30 pre-pulsar shuttle oscillator in which two 15-generation pre-pulsar shuttle mechanisms each composed of two tubs hassle a pre-pulsar. It was found by David Buckingham on August 16, 1980.[1] A slightly different period-30 shuttle can be created by shifting the top half of the shuttle two cells to the left or right (see below). This allows the outermost tubs to optionally be replaced by blocks.
Eureka | |||||||||||
| |||||||||||
View animated image | |||||||||||
View static image | |||||||||||
Pattern type | Oscillator | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Oscillator type | Shuttle | ||||||||||
Number of cells | 28 | ||||||||||
Bounding box | 18×15 | ||||||||||
Period | 30 | ||||||||||
Mod | 15 | ||||||||||
Heat | 22.4 | ||||||||||
Volatility | 0.91 | ||||||||||
Strict volatility | 0.91 | ||||||||||
Discovered by | David Buckingham | ||||||||||
Year of discovery | 1980 | ||||||||||
| |||||||||||
| |||||||||||
| |||||||||||
|
The first known semi-natural appearance of a version of this oscillator was in November 2014 in a soup found by Adam P. Goucher using apgsearch.[2] The monomerized version first occurred in March 2016.[3]
Image gallery
gollark: I mean, as far as I can tell there isn't really a faster *and* more storage-efficient way to do search than the inverted-index page_tokens thing.
gollark: ```sqlCREATE TABLE crawl_queue ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, lockTime INTEGER, added INTEGER NOT NULL, referrer TEXT);CREATE TABLE pages ( id INTEGER PRIMARY KEY, url TEXT NOT NULL UNIQUE, rawContent BLOB NOT NULL, rawFormat TEXT NOT NULL, textContent TEXT NOT NULL, updated INTEGER NOT NULL);CREATE TABLE page_tokens ( id INTEGER PRIMARY KEY, page INTEGER NOT NULL REFERENCES pages(id), token TEXT NOT NULL, weight REAL NOT NULL);CREATE TABLE links ( id INTEGER PRIMARY KEY, toURL TEXT NOT NULL, fromURL TEXT NOT NULL, lastSeen INTEGER NOT NULL, UNIQUE (toURL, fromURL))```Here is the database.
gollark: To be fair, the text content field isn't that necessary, as for search it uses the page_tokens table anyway and it can be rebuilt from the HTML if I need it.
gollark: The frequency of every word *must* be stored for quick (O(log n) time or something) search, the raw HTML or at least might be needed if I come up with a better way to weight frequency or something, the links are useful for (future) better search ranking algorithms.
gollark: But I suppose I could drop the text bit, that can be reconstructed later™ and search doesn't really need it.
References
- Dean Hickerson's oscillator stamp collection. Retrieved on March 14, 2020.
- Adam P. Goucher (November 25, 2014). Re: Soup search results (discussion thread) at the ConwayLife.com forums
- Aidan F. Pierce (March 20, 2016). Re: Soup search results (discussion thread) at the ConwayLife.com forums
This article is issued from Conwaylife. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.