Coumputation subsystem: Difference between revisions
Jump to navigation
Jump to search
a crude start |
m →Why the amount of data to handle is managable despite being enormous: added link to Data IO bottleneck |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 19: | Line 19: | ||
== Why the amount of data to handle is managable despite being enormous == | == Why the amount of data to handle is managable despite being enormous == | ||
TODO | TODO | ||
Related: [[Data IO bottleneck]] | |||
== Related == | == Related == | ||
* [[Data decompression chain]] | * [[Data decompression chain]] | ||
* [[Control hierarchy]] – [[Control levels]] | |||
---- | |||
* [[Nanomechanical computation]] – [[Mechanical computation]] | |||
* [[Mechanical circuit element]] | |||
* [[The mechanoelectrical correspondence]] | |||
---- | |||
* [[Reversible data processing]] | |||
Latest revision as of 00:01, 22 November 2021
A hierarchical system.
- Electronics on larger scales
- Some nanomechanical computation at the smallest scales
- output: mostly open-loop controlling connections to the [[[Drive subsystem of a gem-gum factory]]
- input: High level user interfaces (graphical or otherwise) for human users interfaces
Eventually possible (but not critically necessary!) exotic stuff:
- larger scales than electronics (due to optical wavelengths being big) possibly soem photonci processing
- computation with other physical phenomenons (plasmons, spins, ...)
Why the amount of data to handle is managable despite being enormous
TODO
Related: Data IO bottleneck
Related
- Nanomechanical computation – Mechanical computation
- Mechanical circuit element
- The mechanoelectrical correspondence