20P2

20P2 is a period-2 oscillator composed of a beacon stabilizing an unnamed induction coil (a weld of a dock and a mango).

20P2
<html><div class="rle"><div class="codebox"><div style="display:none;"><code></html> b2o5b$bo6b$4bo3b$3b2o3b2$b4o3b$o4bo2b$2o2bobob$4bo2bo$5bobo$6bo! #C [[ THUMBSIZE 2 THEME 6 GRID GRIDMAJOR 0 SUPPRESS THUMBLAUNCH ]] #C [[ AUTOSTART ]] <nowiki>#C [[ LOOP 2 GPS 2 THUMBSIZE 2 ]]</nowiki> <html></code></div></div><canvas width="200" height="300" style="margin-left:1px;"><noscript></html> <html></noscript></canvas></div></html>
View animated image
View static image
Pattern type Oscillator
Family Beacon
Number of cells 21
Bounding box 8×11
Frequency class 31.2
Period 2
Mod 2
Heat 2
Volatility 0.09
Strict volatility 0.09
Rotor type Diagonal on-off
Discovered by Unknown
Year of discovery Unknown

Commonness

20P2 is about the thirty-fourth most common naturally-occurring oscillator in Achim Flammenkamp's census, being slightly less common than the cis-beacon on cap and the 1 beacon but more common than the cis-beacon down on long hook.[1] It is currently the most common unnamed oscillator.

gollark: If the issue is what I think it could be, then it's accidentally dropping? data on the threshold of the rolling counter region incorrectly.
gollark: ```nimproc pollTargets(ctx: Ctx) {.async.} = for row in ctx.db.all("SELECT * FROM sites"): var (id, url, rollingTotalPings, rollingSuccessfulPings, rollingLatency, rollingDataSince) = row.unpack((int64, string, int64, int64, int64, Option[Time])) let res = await ctx.pollTarget(url) let threshold = getTime() # drop old data from rolling counters if rollingDataSince.isSome: for row in ctx.db.iterate("SELECT status, latency FROM reqs WHERE timestamp >= ? AND timestamp <= ? AND site = ?", rollingDataSince.get, threshold, id): let (statusRaw, latency) = row.unpack((int, int)) rollingTotalPings -= 1 rollingLatency -= latency if statusRaw <= 0: rollingSuccessfulPings -= 1 # add new data rollingTotalPings += 1 rollingLatency += res.latency if int(res.rtype) <= 0: rollingSuccessfulPings += 1 ctx.db.transaction: ctx.db.exec("UPDATE sites SET rc_total = ?, rc_success = ?, rc_latency = ?, rc_data_since = ? WHERE sid = ?", rollingTotalPings, rollingSuccessfulPings, rollingLatency, threshold, id) ctx.db.exec("INSERT INTO reqs (site, timestamp, status, latency) VALUES (?, ?, ?, ?)", id, getTime(), int(res.rtype), res.latency)```This is the core algorithm.
gollark: Actually, æææææ who even knows.
gollark: The boundary conditions could be wrong on this query.
gollark: Hmm. I think I might know what this is maybe?

References
  1. Achim Flammenkamp (September 7, 2004). "Most seen natural occurring ash objects in Game of Life". Retrieved on January 15, 2009.
  • 21P2.1593 at Heinrich Koenig's Game of Life Object Catalogs
This article is issued from Conwaylife. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.