👨🏿‍🦱
Showing posts with label computation. Show all posts
Showing posts with label computation. Show all posts

#OpusSolve

P versus NP

P versus NP

Story

Errata

Presented here are wrong/incorrect approaches to tackling the problem. These are offered as case studies of what to avoid.

/The Origamic Symphony🎶 [computation]

Composer: 🧑🏿Link Starbureiy
As a signal, The Origamic Symphony™℗ (Q) :== runtime normalizing (hyper/hypo = 0) lnq🧑🏿's movements. It is improvised/composed for solo joey🐨🪀.
/// This represents the totality of keys in sequence, forming the basis of our playback.

Resting atop the hypothesis that every brane arrangement is (geometrically) convertible, solvable, and scorable, Q♯ is responsive to the calculus of Egglepple resonances (the program of the portfolio imagined as frets pertinent to stereotyping STU).


"There is this beautiful symphony playing - everywhere, all the time."^ - 🧑🏿lnq


The symphony treats the entire portfolio as a (single loopstring➿*) path integral (line) subject to integration (including integration-by-parts [the twisting of pencils✏️]) and derivation.** A continuous function. -- All walks are integrated in twistorspace, and output some stew derivative. (see mathemusic, preimage/image, UUelcome, Q♭, joey🎻, UUhistlegrass, 🧑🏿lnq's Starting Five, Juke Lemma, crypto compliance)
/// +The Origamic Symphony is the subject of 🧑🏿lnq's recital. -- Egglepple can also be thought of as the signal relay.
+Here "origami" specifies "p-brane (membrane/frame) folding". Namely, it is the twisting of measures (length) between the Planck and nano data.

/kernel (operating system)

/P versus NP problem

/user space

(see also UUe interface, avatar)

/server (computing)

/supercomputer