VrlWiki - User contributions [en]

Agenda and action items for CALLIT2

2009-10-20T13:17:42Z

John Huffman:

==Screens:==
*How visible are the seems
*are the seems better/worse than vignetting
*How much more distorted will the image be for non tracked users
*How does the transition from wall to floor look
*how are the screens attached to the frame
*how rigid are the screens, is there any sway
*Do they have problems keeping them clean
*Are they prepared if a screen is damaged, needs replacement
==Projectors:==
*How well aligned are the projectors to the screens
*How well are the projector pairs aligned to each other
*How far away are the projectors (projector throw)
*Do they do any type of projector blending

==Computer/Software:==
*What software are they using to drive the displays
*How are the computers tied together, any special networking
*What computer configuration are they using
*What graphics cards
*What OS
== Color Balance: ==
*I would like to look at color balance adjustments
*Are they using any type of aid to adjust color balance

Agenda and action items for CALLIT2

2009-10-20T13:17:26Z

John Huffman: New page: ==Screens:== *How visible are the seems *are the seems better/worse than vignetting *How much more distorted will the image be for non tracked users *How does the transition from wall to f...

==Screens:==
*How visible are the seems
*are the seems better/worse than vignetting
*How much more distorted will the image be for non tracked users
*How does the transition from wall to floor look
*how are the screens attached to the frame
*how rigid are the screens, is there any sway
*Do they have probles keeping them clean
*Are they prepared if a screen is damaged, needs replacement
==Projectors:==
*How well alligned are the projectors to the screens
*How well are the projector pairs alligned to each other
*How far away are the projectors (projector throw)
*Do they do any type of projector blending

==Computer/Software:==
*What software are they using to drive the displays
*How are the computers tied together, any special networking
*What computer configuration are they using
*What graphics cards
*What OS
== Color Balance: ==
*I would like to look at color balance adjustments
*Are they using any type of aid to adjust color balance

Agenda and action items for Disney Imagineering

2009-10-20T13:16:11Z

John Huffman:

Here are just some of the questions we should ask when visitng Disney Imagineering:

== Color Balance: ==

*I would like to look at color balance adjustments
*Are they using any type of aid to adjust color balance

== Tiling: ==

*How well are the displays tiled, is there any gap, or do they overlap
*At what angle are the discreet tiles visible.
*How large of an area is the "sweet spot"

==Screen: ==

*How much does the curved screen affect the projection
*Is the screen they use better/worse than the provided screen
*How is the screen attached

== TV: ==

*How was the screen removed, and do you gain pixels by removing it
*Is the display still stable with he screen removed
*How is the system mounted into the frame
*How do they compensate for the bezel at the bottom
*Have they had any significant hardware failures
*Can a system be easily replaced if it dies
*Want to see display running is stereo, so we can witness non-sync

==Computer/Software:==
*What software are they using to drive the displays
*How are the computers tied together, any special networking
*What computer configuration are they using
*What graphics cards
*What OS

==Extras:==
*What are the using for input/control
*Do they use any type of tracking
*what stereo glasses do they use

Agenda and action items for Disney Imagineering

2009-10-20T13:01:14Z

John Huffman:

Here are just some of the questions we should ask when visitng Disney Imagineering:

== Color Balance: ==

*I would like to look at color balance adjustments
*Are they using any type of aid to adjust color balance

== Tiling: ==

*How well are the displays tiled, is there any gap, or do they overlap
*At what angle are the discreet tiles visible.
*How large of an area is the "sweet spot"

==Screen: ==

*How much does the curved screen affect the projection
*Is the screen they use better/worse than the provided screen
*How is the screen attached

== TV: ==

*How was the screen removed, and do you gain pixels by removing it
*Is the display still stable with he screen removed
*How is the system mounted into the frame
*How do they compensate for the bezel at the bottom
*Have they had any significant hardware failures
*Can a system be easily replaced if it dies
*Want to see display running is stereo, so we can witness non-sync

==Extras:==
*What are the using for input/control
*Do they use any type of tracking
*what stereo glasses do they use

Agenda and action items for Disney Imagineering

2009-10-20T12:58:00Z

John Huffman: New page: Here are just some of the questions we should ask when visitng Disney Imagineering: == Color Balance: == *I would like to look at color balance adjustments *Are they using any type of a...

New CAVE Design

2009-10-20T12:52:23Z

John Huffman: /* Upcoming Trip to Californina */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]
* [[Action Items for Sept. 29th, 2009]]

== Initial Design Issues ==

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Software: commercial quality ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

=== Software: researcher/developer tools ===

* [[Cave Software Overview]]
* [[VRG3D Requirements]]

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

=== Upcoming Trip to Californina ===
*[[Agenda and action items for Disney Imagineering]]
*[[Agenda and action items for CALLIT2]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

New CAVE Design

2009-10-20T12:51:45Z

John Huffman: /* Schedule, Timeline, and Deliverables */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Weekly Cave action items ==
Below is a list of action items for each Cave design meeting.
* [[Action Items for Sept. 15th, 2009]]
* [[Action Items for Sept. 22nd, 2009]]
* [[Action Items for Sept. 29th, 2009]]

== Initial Design Issues ==

=== Display Surface Angles ===
Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries ===
Assigned to SGF. Updates are due on 9/14 by 12:00 noon
* Problem: What are the consequences of tiling displays together?
* Input needed
** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Setup 2 displays and report on artifacts at edge between them (color, geometry)
* Decision: ?

=== Will commodity DLP projection technology work ===
* Problem: Are commodity DLP projection technologies high-enough quality & reliable for a next-gen Cave?
* Input needed
** An understanding of how much effort Mark Mine et al. at Disney have put in
** What is Mark's estimate on how much more time/effort it will take to have a high-quality display
** standard desktop text does not look good on Mitsubishi HDTVs. Is that a "show stopper"?
** Why is a projector-based system worse than HDTV approach?
* Experiments needed
** ?
* Decision: ?

=== Text with Checkerboard Stereo ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?
* Input needed
** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)
* Experiments needed
** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.
* Decision: ?

=== Floor Design === Assigned to SGF.
Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options ===
( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator ===
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Problem: Would camera-based tracking be a value or time-sink for the Cave?
* Input:
** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)
* Experiments needed:
** Try first hand most promising camera-based tracking and document:
*** the degree to which it is: wireless, accurate, low-latency, unobtrusive
*** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of "phicons"/props
* Decision: ?

=== Hardware supporting usability studies ===
Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Software: commercial quality ===
Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)
* Experiments:
** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)
** << who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study >>
* Decision:

=== Software: researcher/developer tools ===

* [[Cave Software Overview]]
* [[VRG3D Requirements]]

== Schedule, Timeline, and Deliverables ==
Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

=== Upcoming Trip to Californina ===
[[Agenda and action items for Disney Imagineering]]
[[Agenda and action items for CALLIT2]]

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

3D Tracking options

2009-09-15T17:50:58Z

John Huffman: /* Hept-Cave Tracking system: */

== Hept-Cave Tracking system: ==

Questions that need to be answered:
*Type of tracking system needed
*Area to track
*Adaptability

Possible vendors/products to consider:

* Vicon[http://www.vicon.com/]
* Qualisys[http://www.qualisys.com/]
* Optitrack[http://www.naturalpoint.com/optitrack/products/flex-v100r2/]
* Phasespace[http://www.phasespace.com/]

3D Tracking options

2009-09-15T17:48:08Z

John Huffman: New page: == Hept-Cave Tracking system: == Questions that need to be answered: * Type of tracking system needed * Area to track * Adaptability Possible vendors/products to consider: * Vicon[ht...

== Hept-Cave Tracking system: ==

Questions that need to be answered:
* Type of tracking system needed
* Area to track
* Adaptability

Possible vendors/products to consider:

* Vicon[http://www.vicon.com/]
* Qualisys[http://www.qualisys.com/]
* Optitrack[http://www.naturalpoint.com/optitrack/products/flex-v100r2/]
* Phasespace[http://www.phasespace.com/]

New CAVE Design

2009-09-15T17:37:58Z

John Huffman: /* Initial Design Issues */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Initial Design Issues ==

=== Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon

=== Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?

=== Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Goals: wireless, accurate, low-latency, unobtrusive
* Examples: head-tracking, tracking fingers and body, tracking "phicons"/props
* Q: Is camera-based tracking reliable in a Cave?

=== Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Decision:

== Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

New CAVE Design

2009-09-15T17:36:50Z

John Huffman: /* Year 1 (0.50 hw-person FTE +consulting) */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Initial Design Issues ==

=== Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon

=== Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?

=== Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== 3D Tracking options === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Goals: wireless, accurate, low-latency, unobtrusive
* Examples: head-tracking, tracking fingers and body, tracking "phicons"/props
* Q: Is camera-based tracking reliable in a Cave?

=== Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Decision:

== Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* Install replacement tile wall, temporary system (month 11)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)

New CAVE Design

2009-09-15T17:35:40Z

John Huffman: /* Year 1 (0.50 hw-person FTE +consulting) */

=Hept-Cave Design Wiki=

This page serves as a repository of the design issues, knowledge, and decisions for the new Brown Cave funded through an NSF grant from 2009-2013.

== Initial Design Issues ==

=== Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.

* Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?
* Input needed
** Expert feedback from Acevedo re KAUST design choices
* Experiments needed
** Set up two side-by-side and top/bottom displays and evaluate anecdotally
* Decision: ?

=== Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon

=== Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What text resolution will be usable with checkerboard stereo and will that level be sufficient to do the experiments and applications that we want to do?

=== Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

=== Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: Would contracting to an integrator to build based on an RFP be effective?
* Input:
** Phone feedback from some of the potential integrators
* Decision:

=== 3D Tracking options === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.
* Goals: wireless, accurate, low-latency, unobtrusive
* Examples: head-tracking, tracking fingers and body, tracking "phicons"/props
* Q: Is camera-based tracking reliable in a Cave?

=== Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?
* Input needed
** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)
** Mel says, "[we use] a device called Nexus 4, which has skin conductance, ECG, respiration, and can also be used for EMG and EEG. I think that it is of the order of 10K or less depending on how many channels are used.".
** Consider whether results from future (or past) studies would be significantly improved with such devices?
*** asf thoughts (may be wrong!): GSR helps detects changes in a person's "comfort"-- this might reflect the level of frustration or happiness while evaluating some user interaction or visualization method that the person doesn't verbalize; that may be useful additional information for formal studies. PTSD studies would benefit from the information, I should think. However, if the device requires stringing wires all around, it might cause subjects to behave differently which would be bad.
* Experiments needed
** none
* Decision: ?

=== Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.

* Problem: What do we need to do to make sure that commercial software will be usable in our new facility?
* Input:
** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)
* Decision:

== Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.

The following describes our schedule, timeline, and
deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).

== Year 1 (0.50 hw-person FTE +consulting) ==

We will finalize hardware decisions which will
involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s
equipment; consultation regarding details of acquiring, machining, and integrating elements; and
ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment
will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave
will be taken down and removed.

* Acquire test projection system(s) (month 1)
* Acquire test graphics system(s) (month 1)
* Acquire test tracking system(s) (month 1)
* multi-site visit, design discussions, consultent visits (month 1 - month 3)
* finalize refined design (due month 3, 1.5 hw-person mos)
* order additional wall/test equipment (month 2)
* Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)
* order Cave equipment (due month 5, 1.0 hw-person mos) screens; projectors;computer parts, racks; computer interconnect; computer-display connections; display-display interconnections; display calibration hardware/software; tracking hardware.
* receive equipment (due month 8, 0.5 hw-person mos)
* computer cluster assembled (due month 11, 1 hw-person mo) machine/construct/assemble computer supports; assemble computer hw with high-speed interconnect; install and test OS on cluster
* raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)
* remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)

== Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==
In year 2 we will complete construction of the
display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin
testing individual and linked systems.
* display hardware (due month 20, 4.5 hw-person mos, +machining/fab), (will start in year 1) detailed screen support specifications; detailed monitor support specifications; machine and construct screen supports; machine and construct projector platforms; mount screens and projectors; rough-calibrate projectors
* display-computer interconnect (due month 20, 0.5 hw-person mo)
* tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing
* VRG3D display software library (due month 23, 6 swe-person mos) source-control setup; ability to distribute software configurable for arbitrary multi-display devices; implemented for new display configuration; multi-display optimizations incorporated; tracking incorporated; hooks for automated testing incorporated
* install Avizo (due month 23, 1 swe-person mos)
== Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==
Monitoring and testing reliability software will be
designed, developed, and deployed. Application users and developers will be able to begin using the system.
* VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library
* distribution version of VRG3D available (due month 30, 1 swe-person mos)
* application users can now begin creating new applications
* monitoring/testing reliability software (due month 30, 2 hw-person mos, 4.5 swe-person mos) daily builds of software library and application; daily tests of machine accessibility (tracking, compute cluster functionality/performance, display device availability); touchscreen display of component status/availability; touchscreen access to troubleshooting options; easily extensible touchscreen interface for startup of (experiments, applications, demos, homework assignments) item displayfacet alignment system (due month 35, 5.5 hw-person mos)

== Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) ==
In year 4 we will finalize the software infrastructure,
complete the auto-calibration system.
* software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)
(note that these are not maintenance, but part of the development process); feature request from
specific application areas; application users will change apps to use them
* final software distributions to SourceForge (due month 47, 1 swe-person mos)