Sensebridge: Difference between revisions

From Noisebridge
Jump to navigation Jump to search
No edit summary
No edit summary
 
(42 intermediate revisions by 16 users not shown)
Line 1: Line 1:
{{projects}}
{{historic}}
=Sensebridge: The Noisebridge Cyborg Group=
=Sensebridge: The Noisebridge Cyborg Group=
[[Image:CoinTypePagerMotors.jpg|right|350px|title|Coin Type pager Motor]]


"If you can't beat the robot armies, join them."
"If you can't beat the robot armies, join them."


We are concerned with human-machine interfaces.
We are concerned with human-machine interfaces.


==Motivations==
==Motivations==
Line 15: Line 19:
To avoid confusion (where possible) we'll try to use these terms.
To avoid confusion (where possible) we'll try to use these terms.


"Sensor" is the device that detects external stuff that the body (probably) can't detect.  "Display" is the way the device shows data to the body (not necessarily visually).  This gets around the device-centric / body-centric problem that shows up when using the terms input & output.  "Armature" is the physical component of the device: the belt, hat, armband, etc; distinct from the electronics.
"Sensor" is the device that detects external stuff that the body (probably) can't detect.  Sensors can be divided into those that sense the world, and those that digitize a user's actions.  The latter are more commonly called "human input devices", (HID's).
 
"Display" is the way the device shows data to the body (not necessarily visually).  This gets around the device-centric / body-centric problem that shows up when using the terms input & output.   
 
"Armature" is the physical component of the device: the belt, hat, armband, etc; distinct from the electronics.


==Mailing List==
==Mailing List==
Line 23: Line 31:
==Component Sourcing==
==Component Sourcing==


Here are pages for discussing [[Sensors|sensors]], [[Displays|displays]], and [[Armatures|armatures]] in terms of price and usability.  They also include a list of all known/speculated types of each.
Here are pages for discussing:


==Stimulus Sensor and Input Method Common API==
===[[Sensors|sensors]]===
detect a property of the world
 
===[[Displays|displays]]===
communicate it to the body/mind
===[[Armatures|armatures]]===
hold the above together and in the proper place on the body
 
They also include a list of all known/speculated types of each.
 
==Sensor and Display API==


*What might that mean?
*What might that mean?
Line 33: Line 51:


*Why?
*Why?
**Plug-and-play(ish) interoperability of sensors and input modes. Build three sensors and three input modes, and we have 9 possible combinations, und so weiter.
**Plug-and-play(ish) interoperability of sensors and displays. Build three sensors and three displays, and we have 9 possible combinations, und so weiter.
**Simplify development by separating sensing and presentation design/tasks.
**Simplify development by separating sensing and presentation design/tasks.


Line 41: Line 59:
**#Abstract away from the physical phenomena the stimuli represent and look instead at common patterns in the data streams.
**#Abstract away from the physical phenomena the stimuli represent and look instead at common patterns in the data streams.
**#???
**#???
**On the data presentation end:
**On the data display end:
**#Identify and prototype a number of input methods.
**#Identify and prototype a number of display methods.
**#For each method think of:
**#For each method think of:
**#*What modulations of the signal are possible; intensity, spacing, direction, timing...? Based on that, what is the theoretical bandwidth of that input method?
**#*What modulations of the signal are possible; intensity, spacing, direction, timing...? Based on that, what is the theoretical bandwidth of that method?
**#*How sensitive is the average person there? How much of the signal can the brain interpret meaningfully (too much noise vs. too weak of a signal)? Based on that, what is the <em>practical</em> bandwidth that we might expect?
**#*How sensitive is the average person there? How much of the signal can the brain interpret meaningfully (too much noise vs. too weak of a signal)? Based on that, what is the <em>practical</em> bandwidth that we might expect?


==Current Projects==
==Current Projects==
[[Compass Vibro Anklet|Compass Vibro-Anklet]]
[[Compass Vibro Anklet|Compass Vibro-Anklet]]
[[Eyes in the back of your back]]
[[Tongue Tingler|Tongue Tingler (Trans-lingual Electric Nerve Stimulator)]]
[[Free hands input device]]
[[Pulse Necklace]]
[[QuickLook Displays]]
[[UltraSonicHearing|Ultrasonic Hearing / Echolocation]]
[[TechnicolorDreamcoat|Technicolor Dreamcoat]]
[[List of senses we do not possess]]
===Miscellaneous Distractions===
[http://pony.noisebridge.net/~cmaier/recherche_du_temps_perdu/ Edible interconnects]


==Cybernetic Theory==
==Cybernetic Theory==
Line 55: Line 95:


Pseudo-cybernetic loop showing neural integration of artificial sensory system, [https://www.noisebridge.net/images/8/8f/Sensory_Addition_%281.5_order%29.jpg diagram].
Pseudo-cybernetic loop showing neural integration of artificial sensory system, [https://www.noisebridge.net/images/8/8f/Sensory_Addition_%281.5_order%29.jpg diagram].
[http://en.wikipedia.org/wiki/Cybernetic Cybernetics page on Wikipedia]




Line 72: Line 114:


[[Lamont's PWM code]]
[[Lamont's PWM code]]


==Meeting Notes==
==Meeting Notes==
Line 80: Line 123:


[[NBC_2009Mar29|March 29, 2009]]
[[NBC_2009Mar29|March 29, 2009]]
[[NBC_2009Apr05|April 5, 2009]]
[[NBC_2009Apr19|April 19, 2009]]
(the meetings continue apace; the minutes, sadly not)
[[NBC_2009July12|July 12, 2009]]
[[NBC_2009July13|Hack Session July 13, 2009]]
[[NBC_2009July19|July 19, 2009]]
[[NBC_2009August2|August 2, 2009]]
[[NBC_2009October4|Oct 4, 2009]]


[[Category:Sensebridge]]
[[Category:Sensebridge]]
[[Category:Neuro]]

Latest revision as of 14:57, 3 March 2022

Noisebridge | About | Visit | 272 | Manual | Contact | Guilds | Resources | Events | Projects | 5MoF | Meetings | Donate | (Edit)
Projects | Concepts | Proposals | Art | Spacebridge | PFA Template | (Edit)
Oldcomputer.png
Note: This page is for historic purposes only. It does not apply to modern Noisebridge. | Edit

Sensebridge: The Noisebridge Cyborg Group[edit]

Coin Type pager Motor

"If you can't beat the robot armies, join them."

We are concerned with human-machine interfaces.


Motivations[edit]

We want to "make the invisible visible", to bridge our senses. Many group members were inspired years ago by this awesome Wired article, which describes obtaining an unerring sense of direction via a compass belt. Is the brain really plastic enough to adapt to entirely new senses? How natural would it feel after you've fully adapted? Then what happens when you take the device off?

What new sense do you want? What existing sense might it map onto?

Terminology[edit]

To avoid confusion (where possible) we'll try to use these terms.

"Sensor" is the device that detects external stuff that the body (probably) can't detect. Sensors can be divided into those that sense the world, and those that digitize a user's actions. The latter are more commonly called "human input devices", (HID's).

"Display" is the way the device shows data to the body (not necessarily visually). This gets around the device-centric / body-centric problem that shows up when using the terms input & output.

"Armature" is the physical component of the device: the belt, hat, armband, etc; distinct from the electronics.

Mailing List[edit]

We have created a cyborg mailing list on the Noisebridge server. Please join us!

Component Sourcing[edit]

Here are pages for discussing:

sensors[edit]

detect a property of the world

displays[edit]

communicate it to the body/mind

armatures[edit]

hold the above together and in the proper place on the body

They also include a list of all known/speculated types of each.

Sensor and Display API[edit]

  • What might that mean?
    • A standard protocol that can:
      1. encompass most sensory data of the sort we are interested in researching
      2. allow for presentation of any those data through any of a wide variety of modalities
  • Why?
    • Plug-and-play(ish) interoperability of sensors and displays. Build three sensors and three displays, and we have 9 possible combinations, und so weiter.
    • Simplify development by separating sensing and presentation design/tasks.
  • How?
    • On the data sensing end:
      1. Identify a primary set of interesting stimuli, consider various encodings thereof.
      2. Abstract away from the physical phenomena the stimuli represent and look instead at common patterns in the data streams.
      3. ???
    • On the data display end:
      1. Identify and prototype a number of display methods.
      2. For each method think of:
        • What modulations of the signal are possible; intensity, spacing, direction, timing...? Based on that, what is the theoretical bandwidth of that method?
        • How sensitive is the average person there? How much of the signal can the brain interpret meaningfully (too much noise vs. too weak of a signal)? Based on that, what is the practical bandwidth that we might expect?

Current Projects[edit]

Compass Vibro-Anklet

Eyes in the back of your back

Tongue Tingler (Trans-lingual Electric Nerve Stimulator)

Free hands input device

Pulse Necklace

QuickLook Displays

Ultrasonic Hearing / Echolocation

Technicolor Dreamcoat


List of senses we do not possess

Miscellaneous Distractions[edit]

Edible interconnects

Cybernetic Theory[edit]

Cybernetic loop of GPS + vibrating hat, diagram.

Pseudo-cybernetic loop showing neural integration of artificial sensory system, diagram.

Cybernetics page on Wikipedia


Links[edit]

Youtube of experimenter stimulating his face with small electrical pulses to produce externally controlled movements: http://www.youtube.com/watch?v=dy8zUHX0iKw

http://transcenmentalism.org/OpenStim/tiki-index.php

http://openeeg.sourceforge.net/doc/

http://www.biotele.com/ - remote control cockroach

http://www.instructables.com/id/Breath-powered-USB-charger/

VibroHat in action at BIL 2008: http://www.flickr.com/photos/quinn/2307779651/in/photostream/

Lamont's PWM code


Meeting Notes[edit]

March 15, 2009

March 22, 2009

March 29, 2009

April 5, 2009

April 19, 2009

(the meetings continue apace; the minutes, sadly not)

July 12, 2009

Hack Session July 13, 2009

July 19, 2009

August 2, 2009

Oct 4, 2009