Adjunct Reality Systems - Revision history

Ezrec at 12:45, 3 June 2008

2008-06-03T12:45:55Z

← Older revision		Revision as of 12:45, 3 June 2008
Line 29:		Line 29:
	== Positioning System ==		== Positioning System ==

	~~GPS? Magnetics?~~		Accelerometers for small deltas, but most position information is provided by bar-coded IR reflective tape.

	IR tape on walls?		The IR emitter on the device 'blinks' at a pseudo random rate, allowing the removal of constant non-mapped IR sources (candles, incandescent lights, etc).

			IR reflective tape on walls and surfaces:
	* Passive		* Passive
			* Cheaper than active positioning devices
	* Can embed bar codes or other graphic elements		* Can embed bar codes or other graphic elements
	* Can be filtered out of the visual overlay.		* Can be filtered out of the visual overlay.

Ezrec: /* Project Planning */

2008-05-19T18:18:21Z

Project Planning

← Older revision		Revision as of 18:18, 19 May 2008
Line 126:		Line 126:
	** Using an IR emitter and camera, demonstrate the ability to track multiple pieces of IR reflective tape in the environment. Tape may be made 'unique' by encoding them with barcodes of non-reflective regions. (bullseye barcodes highly suggested)		** Using an IR emitter and camera, demonstrate the ability to track multiple pieces of IR reflective tape in the environment. Tape may be made 'unique' by encoding them with barcodes of non-reflective regions. (bullseye barcodes highly suggested)
	** Using accelerometers mounted to a conventional camera, demonstrate the ability to keep a 0.5 meter virtual sphere overlayed into the center of the room as the camera moves around it. Latency issues and "drift" are acceptable at this milestone, but a plan must exists for reducing them to acceptable limit by the next milestone.		** Using accelerometers mounted to a conventional camera, demonstrate the ability to keep a 0.5 meter virtual sphere overlayed into the center of the room as the camera moves around it. Latency issues and "drift" are acceptable at this milestone, but a plan must exists for reducing them to acceptable limit by the next milestone.
	** Demonstrate a prototype GUI (using an existing multi-~~tough~~ interface such as WII remotes or an iPhone) that corresponds to the prototype specification.		** Demonstrate a prototype GUI (using an existing multi-touch interface such as WII remotes or an iPhone) that corresponds to the prototype specification.

	=== M3: Hulking Prototype ===		=== M3: Hulking Prototype ===
Line 145:		Line 145:
	* Software activities		* Software activities
	** Get all software components to run on the 'hulking prototype'		** Get all software components to run on the 'hulking prototype'
	** Demonstrate all of the 'Core ~~Applications~~' from the [[ARS Prototype Specification]]		** Demonstrate all of the 'Core Demonstrations' from the [[ARS Prototype Specification]]

	=== M4: Investor Prototype ===		=== M4: Investor Prototype ===
Line 161:		Line 161:
	* Software activities:		* Software activities:
	** Get all software components to run on the wearable prototype		** Get all software components to run on the wearable prototype
	** Demonstrate all of the 'Core ~~Applications~~' from the [[ARS Prototype Specification]]		** Demonstrate all of the 'Core Demonstrations' from the [[ARS Prototype Specification]]
	** Demonstrate at least two of the 'Market Demonstrations' from the [[ARS Prototype Specification]]		** Demonstrate at least two of the 'Market Demonstrations' from the [[ARS Prototype Specification]]

Ezrec: /* Eyepiece */

2008-05-19T03:08:20Z

Eyepiece

← Older revision		Revision as of 03:08, 19 May 2008
Line 10:		Line 10:

	* WII Remote (IR camera, accelerometers)		* WII Remote (IR camera, accelerometers)
			* see-through video eyepieces [http://www.tfot.info/articles/54/lumus-future-video-eyeglasses.html]
			* 'Spy' eyeglass cameras [http://www.pimall.com/NAIS/sunglasscam-nais.html]

	== Pointing Device ==		== Pointing Device ==

Ezrec: /* M6: ??? */

2008-05-19T03:01:56Z

M6: ???

← Older revision		Revision as of 03:01, 19 May 2008
Line 180:		Line 180:

	To be determined by market forces.		To be determined by market forces.


			[[Category:Adjunct Reality Systems]]

Ezrec: /* M3: Hulking Prototype */

2008-05-19T01:58:32Z

M3: Hulking Prototype

@@ Line 128: / Line 128: @@
 === M3: Hulking Prototype ===
 Cost: TBD
@@ Line 133: / Line 134: @@
 ** Ensure all employees are paid for milestone M2
 ** Keep M3 on track
 * Hardware activities:
-**
+** Schematics for wearable prototype

Ezrec: New page: = Introduction = Proposal for a wearable system providing a visual field overlay, synchronized with the wearer's head position and the geometric position of the outside world. = System C...

2008-05-19T01:40:01Z

New page: = Introduction = Proposal for a wearable system providing a visual field overlay, synchronized with the wearer's head position and the geometric position of the outside world. = System C...

New page

= Introduction =

Proposal for a wearable system providing a visual field overlay, synchronized with the wearer's head position and the geometric position of the outside world.

= System Components =

== Eyepiece ==

Glasses with IR emitter, cameras (RGB + IR), accelerometers, and laser-projected visual displays, see the following for current technologies:

* WII Remote (IR camera, accelerometers)

== Pointing Device ==

Passive device with and IR reflective component. Used by the eyepiece to determine the user's pointing locations.

Multiple pointing locations are supported.

== Processing System ==

Internet connected, wireless system. Should be light enough to fit in a hat/helm (with eyepiece attached, like a motorcyclist's "brain bucket" with attached glasses) or embedded in the glasses.

Battery life must be >8 hours.

'''Perceived''' response time to user motion (head or pointing device) must be under 20ms. Anticipatory computation is allowed to close the latency gap.

== Positioning System ==

GPS? Magnetics?

IR tape on walls?
* Passive
* Can embed bar codes or other graphic elements
* Can be filtered out of the visual overlay.

= System Use Cases =

== Covert Office ==

You can have a completely empty office, where even external physical documents are 'scanned in' by the user's cameras.

All user information is 'pasted' on blank walls and desks, and only those who are wearing the system and have the appropriate permissions can see the documents.

== Game Room ==

Full-room gaming in a warehouse space, where all of the reality is replaced by the imaging overlay.

== Crime Scene Recovery ==

Tag and photograph each item in the scene, with markers automatically generated and placed in the user's FOV. The entire crime scene can be reconstructed from the walk through, and the processing software can notify the user of missed areas on-scene.

== Transparent Cockpit ==

Could be used by pilots to replace floor and rear views with external camera views, artificial horizons and landscapes, etc.

If the system fails, overlay is removed.

= Prototype Project =

== Human Resources ==

All human resources should be planned as full-time employees, to be able to meet project deadlines.

* One manager/administrator
** Project management, payment handing, etc.
** Must have accounting credentials
* One hardware engineer
** Hardware design, outsourcing manufacture, etc.
* One firmware engineer
** Implements custom ASICs and firmware for embedded hardware devices
* One user interface software engineer
** Design and implement ARS user interface
* One 3D spatial interface engineer
** Implement 3D tracking and pointer prediction software using IR portion of the cameras
* One image processing software engineer
** Implement RGB image acquisition and stitching over the 3D environment.
** Will use IR tags in the environment to simplify the process.

== Engineering Resources ==

* Hardware lab
** Solder station (scope, picks, etc) for rework
** Logic analyzers
** Data recorders
* NAS Storage
** 100TB (test images, video, etc)
* Compute farm
** 20 2Ghz/4Gb compute blades, in a parallel cluster
*** For automated testing, and simulation of future compute cores for the final product

== Project Planning ==

Project planning shall be milestone based.

Each milestone will have a budget and a deadline. If that budget, plus 50%, is overrun, the project will be canceled. If the milestone deadline is not reached by the agreed upon date plus one month, excepting unusual circumstances, the project will be canceled.

=== M1: Planning ===

Cost: $0

* Secure funding for the expected prototype completion costs plus 50% overrun.
* Secure employee agreements for all required positions.
* All employees must agree to and sign off on the prototype requirement and architecture specifications.
* All employees must agree to and sign off on prototype milestone exit requirements

=== M2: Software Prototype ===

Cost: TBD

* Secure facilities for hardware lab, NAS, and compute farm
** NOTE: This should be a shared access area, that all employees have access to.
* Complete the following administrative activities:
** Purchase and configure the NAS storage
** Purchase and configure the compute farm
** Set up the development/corporate Wiki
** Set up the bug tracking system
** Keep M2 on track.
* Complete the following hardware activities:
** Investigate what vendors are ''immediately'' available for all architected hardware components.
** Support software prototype investigation
* Complete the following firmware activities:
** Support software prototype investigation
* Complete the following software activities:
** Using an IR emitter and camera, demonstrate the ability to track multiple pieces of IR reflective tape in the environment. Tape may be made 'unique' by encoding them with barcodes of non-reflective regions. (bullseye barcodes highly suggested)
** Using accelerometers mounted to a conventional camera, demonstrate the ability to keep a 0.5 meter virtual sphere overlayed into the center of the room as the camera moves around it. Latency issues and "drift" are acceptable at this milestone, but a plan must exists for reducing them to acceptable limit by the next milestone.
** Demonstrate a prototype GUI (using an existing multi-tough interface such as WII remotes or an iPhone) that corresponds to the prototype specification.

=== M3: Hulking Prototype ===

Cost: TBD

* Administrative activities:
** Ensure all employees are paid for milestone M2
** Keep M3 on track
* Hardware activities:
**