http://vrl.cs.brown.edu/wiki/api.php?action=feedcontributions&feedformat=atom&user=Andrew+Forsberg 2026-04-20T02:59:56Z User contributions MediaWiki 1.43.1 http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4467 2010-07-26T14:06:17Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * 360° FOV (vertical sufaces plus ceiling and floor)<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * design must accomodate 3D tracking (ergonomic, &quot;versatile&quot;, full-volume, high-accuracy, low-latency)<br /> ** head/hand tracking critical, we've wanted finger-tip, foot, and prop (e.g., a stylus-tip) tracking in past but '98 Cave could not always do it<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> * Q: is it 8' cube again? what are pros/cons of larger/smaller display?<br /> * Q: Is the software that will drive the display a constraint on complexity of the hardware? how many machines will drive display? 50? does VRG3D and/or other software scale trivially to expected # of machines that will drive it?<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4466 2010-07-26T14:02:52Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * 360° FOV<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * design must accomodate 3D tracking (ergonomic, &quot;versatile&quot;, full-volume, high-accuracy, low-latency)<br /> ** head/hand critical, we've wanted finger-tip, foot, and stylus-tip tracking in past but '98 Cave could not do it<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4465 2010-07-23T20:40:13Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * 360° FOV<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * design must accomodate 3D tracking (ergonomic, &quot;versatile&quot;, full-volume, high-accuracy, low-latency)<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4464 2010-07-23T20:00:21Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * design must accomodate 3D tracking (ergonomic, &quot;versatile&quot;, full-volume, high-accuracy, low-latency)<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4463 2010-07-23T19:59:19Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> * 3D tracking (high accuracy, low-latency, ergonomic, &quot;versatile&quot;)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4462 2010-07-23T19:55:55Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo<br /> * contrast and brightness comparable to today's conventional desktop computer<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=4461 2010-07-23T19:55:06Z

<p>Andrew Forsberg: /* Design Goals */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Design Goals ==<br /> <br /> * 20/30 resolution (== 100dpi desktop monitor?); 20/20 would be a real coup, if possible -- &quot;retina cave&quot;<br /> * seamless; this likely implies overlapped rear projection and rounded corners<br /> * stereo (single user since multi-user not possible w/ available hardare &amp; budget)<br /> * &quot;good enough&quot; contrast and brightness (i.e., comparable to standard desktop computer)<br /> * equipment (hardware plus construction) budget of $1M<br /> * all parts available for order by 9/30/10<br /> * avoid technology unnecessary for primary goals (unless it can change the primary goals)<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> * [[Action Items for Oct. 27th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3980 2010-01-19T15:49:47Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Software should be open-source (e.g., on SourceForge)<br /> # Let new users get started in a few minutes through online documentation<br /> ## Implementation idea: regular diagnostics at the hardware and support-library levels to minimize undetected failures that block users (this needs rephrasing and possibly division into multiple requirements)<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> ## implementation idea: binaries and as source code (what is plan for data distribution?)<br /> # Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> ## implementation idea: provide support for regular testing of applications to minimize code rot<br /> # Capture and disseminate experience<br /> ## implementation idea: outside of software, e.g., stereo pair, stereo video, session state over time, ...<br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> ## implementation idea: A simulator (probably inside VRG3D)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3979 2010-01-15T19:49:07Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> ## Implementation idea: regular diagnostics at the hardware and support-library levels to minimize undetected failures that block users (this needs rephrasing and possibly division into multiple requirements)<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> ## implementation idea: binaries and as source code (what is plan for data distribution?)<br /> # Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> ## implementation idea: provide support for regular testing of applications to minimize code rot<br /> # Capture and disseminate experience<br /> ## implementation idea: outside of software, e.g., stereo pair, stereo video, session state over time, ...<br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> ## implementation idea: A simulator (probably inside VRG3D)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3978 2010-01-15T19:42:20Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> ## Implementation idea: regular diagnostics at the hardware and support-library levels to minimize undetected failures that block users (this needs rephrasing and possibly division into multiple requirements)<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> ## implementation idea: binaries and as source code (what is plan for data distribution?)<br /> # A simulator (probably inside VRG3D)<br /> # Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> ## implementation idea: provide support for regular testing of applications to minimize code rot<br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3977 2010-01-15T19:38:10Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies), binary and/or source<br /> # A simulator (probably inside VRG3D)<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3973 2010-01-12T16:17:57Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> # A simulator (probably inside VRG3D)<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Capture and disseminate experience (outside of software, e.g., stereo pair, stereo video, virtual videography, Q: what to capture? how?)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3972 2010-01-12T16:15:27Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> # A simulator (probably inside VRG3D)<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> # Capture and disseminate experience (outside of software, e.g., as &quot;HD video tapes&quot;, Q: what to capture? how?)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3965 2010-01-05T16:37:13Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> # A simulator (probably inside VRG3D)<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> # Need a scripting interface (e.g., for testing without all hardware available, sharing, &quot;slowing down time&quot;, etc.)<br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3964 2010-01-05T16:32:17Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # Easy to make applications run on other universities systems (dhl: maybe implies small dependencies)<br /> # A simulator (probably inside VRG3D)<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3949 2009-12-15T16:54:58Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Desktop debugging and development environment (so you can run it without a Cave)<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3948 2009-12-15T16:33:28Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;ease-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3947 2009-12-15T16:31:33Z

<p>Andrew Forsberg: </p> <hr /> <div>== High-level goals ==<br /> # Let new users get started in a few minutes through online documentation<br /> # Create rich immersive virtual worlds with high update rates and low-latency<br /> # Easily let applications run on a spectrum of displays ranging from a single conventional monitor to a Cave consisting of 40-60 tiles.<br /> # Provide input and output devices (e.g., tracked glasses, wands, audio, tracked paintbrushes, joysticks, spaceball, Wiimote, etc.)<br /> # Interoperate (to some degree) with geometry and color calibration system<br /> # [MAYBE] Reduce/minimize “code rot” so apps continue to run and can easily be turned into “demos” <br /> <br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;easy-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_Disney_Imagineering&diff=3890 2009-10-27T15:53:09Z

<p>Andrew Forsberg: </p> <hr /> <div>Here are just some of the questions we should ask when visitng Disney Imagineering:<br /> <br /> (Please be sure to carefully run through all of these top-to-bottom.)<br /> <br /> <br /> = General discussion items to cover at some point =<br /> <br /> ==Alternative displays &amp; projection material==<br /> *general discussion on this, commercial TV's come and go quickly..<br /> *Are mfgt's thinking about tiling their displays &amp; getting rid of borders?<br /> *LG borderless display (http://www.electronichouse.com/article/lg_introduces_frameless_plasma_tv/)<br /> *projecting on bezels ([[PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall]])<br /> *when will new LCD displays be available for purchase?<br /> <br /> ==Should it be a surround Cave==<br /> *Discuss pros and cons of a surround Cave (&quot;6-sided&quot; vs an Cave with open side)<br /> *A closed Cave lets you test the value of a closed Cave<br /> *What about two &quot;half-Caves&quot; that can move together &amp; apart?<br /> <br /> <br /> = Technical Details to get into =<br /> <br /> == Color Balance: ==<br /> <br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == Tiling: ==<br /> <br /> *How well are the displays tiled, is there any gap, or do they overlap<br /> *At what angle are the discreet tiles visible. <br /> *How large of an area is the &quot;sweet spot&quot;<br /> <br /> ==Screen: ==<br /> <br /> *How much does the curved screen affect the projection<br /> *Is the screen they use better/worse than the provided screen<br /> *How is the screen attached<br /> <br /> == TV: ==<br /> <br /> *How was the screen removed, and do you gain pixels by removing it<br /> *Is the display still stable with he screen removed<br /> *How is the system mounted into the frame<br /> *How do they compensate for the bezel at the bottom<br /> *Have they had any significant hardware failures<br /> *Can a system be easily replaced if it dies<br /> *Want to see display running is stereo, so we can witness non-sync<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *What is the list of other software options did they consider? (VR Juggler? Others?)<br /> *How are the computers tied together, any special networking? What is latency?<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?<br /> <br /> ==Audio:==<br /> *What audio system is being used? (3D spatialized?)<br /> *How is audio synchronized with visuals? What software?<br /> <br /> ==Haptics:==<br /> *Is there haptics input/output support?<br /> <br /> == Stereo display: ==<br /> *What is the list of work that would make stereo display work? Which are understood and which need research/solutions?<br /> <br /> ==Extras:==<br /> *What are the using for input/control?<br /> *Do they use any type of tracking<br /> *what stereo glasses do they use</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_CALLIT2&diff=3889 2009-10-27T15:51:42Z

<p>Andrew Forsberg: </p> <hr /> <div>==50K-view question:==<br /> *For each Calit2 display, make notes about how it compares to the __immersive experience__ of the 1998 Brown Cave? (seams? head-tracked viewing? working volume size? tracking quality?)<br /> * Make notes about how it compares to the proposed next-gen Cave. (&quot;desktop resolution&quot;? brightness, contrast, seams, 3D tracking quality?)<br /> <br /> ==Alternative displays &amp; projection material==<br /> *general discussion on this, commercial TV's come and go quickly..<br /> *Are mfgt's thinking about tiling their displays &amp; getting rid of borders?<br /> *LG borderless display (http://www.electronichouse.com/article/lg_introduces_frameless_plasma_tv/)<br /> *projecting on bezels ([[PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall]])<br /> *when will new LCD displays be available for purchase?<br /> <br /> ==Should it be a surround Cave==<br /> *Discuss pros and cons of a surround Cave (&quot;6-sided&quot; vs an Cave with open side)<br /> *A closed Cave lets you test the value of a closed Cave<br /> *What about two &quot;half-Caves&quot; that can move together &amp; apart?<br /> <br /> ==Screens:==<br /> *How visible are the seams<br /> *are the seams better/worse than vignetting<br /> *How much more distorted will the image be for non tracked users<br /> *How does the transition from wall to floor look<br /> *how are the screens attached to the frame<br /> *how rigid are the screens, is there any sway<br /> *Do they have problems keeping them clean<br /> *Are they prepared if a screen is damaged, needs replacement<br /> ==Projectors:==<br /> *How well aligned are the projectors to the screens<br /> *How well are the projector pairs aligned to each other<br /> *How far away are the projectors (projector throw)<br /> *Do they do any type of projector blending<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == Color Balance: ==<br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_CALLIT2&diff=3888 2009-10-27T15:43:35Z

<p>Andrew Forsberg: /* 50K-view question: */</p> <hr /> <div>==50K-view question:==<br /> *For each Calit2 display, make notes about how it compares to the __immersive experience__ of the 1998 Brown Cave? (seams? head-tracked viewing? working volume size? tracking quality?)<br /> * Make notes about how it compares to the proposed next-gen Cave. (&quot;desktop resolution&quot;? brightness, contrast, seams, 3D tracking quality?)<br /> <br /> ==Alternative displays &amp; projection material==<br /> *general discussion on this, commercial TV's come and go quickly..<br /> *Are mfgt's thinking about tiling their displays &amp; getting rid of borders?<br /> *LG borderless display (http://www.electronichouse.com/article/lg_introduces_frameless_plasma_tv/)<br /> *projecting on bezels ([[PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall]])<br /> *when will new LCD displays be available for purchase?<br /> <br /> ==Screens:==<br /> *How visible are the seams<br /> *are the seams better/worse than vignetting<br /> *How much more distorted will the image be for non tracked users<br /> *How does the transition from wall to floor look<br /> *how are the screens attached to the frame<br /> *how rigid are the screens, is there any sway<br /> *Do they have problems keeping them clean<br /> *Are they prepared if a screen is damaged, needs replacement<br /> ==Projectors:==<br /> *How well aligned are the projectors to the screens<br /> *How well are the projector pairs aligned to each other<br /> *How far away are the projectors (projector throw)<br /> *Do they do any type of projector blending<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == Color Balance: ==<br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3887 2009-10-27T15:41:08Z

<p>Andrew Forsberg: /* University facility */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers in general?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3886 2009-10-27T15:40:44Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === University facility ===<br /> * Problem: What are the requirements for University researchers?<br /> * Input needed<br /> ** Interview existing Cave-users and potential Cave-users to consider needs/requirements<br /> * Experiments needed<br /> ** (None?)<br /> * Decision: ?<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=PrePrint:_Tiled%2B%2B:_An_Enhanced_Tiled_Hi-Res_Display_Wall&diff=3885 2009-10-27T15:32:28Z

<p>Andrew Forsberg: New page: PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall via IEEE Transactions on Visualization and Computer Graphics on 7/30/09 In recent years, high-resolution displays have become incr...</p> <hr /> <div>PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall<br /> via IEEE Transactions on Visualization and Computer Graphics on 7/30/09<br /> <br /> In recent years, high-resolution displays have become increasingly important to decision makers and scientists, because large screens combined with a high pixel count facilitate content rich, simultaneous display of computer-generated imagery and high-definition video data from multiple sources. Tiled displays are attractive due to their extended screen real estate, scalability, and low cost. One of the drawbacks of LCD-based tiled displays is the fact that users sometimes get distracted by the screens’ bezels, which cause discontinuities in rendered images. Most conventional solutions either ignore the bezels and display all pixels, causing objects to become distorted, or eliminate pixels that would normally fall under the bezels, causing pixels to be missing in the display. In this paper we present a new scalable approach that neither leads to discontinuities nor significant loss of information. By projecting onto the bezels, we demonstrate that a combination of LCD-based tiled displays and projection significantly reduces the bezel problem. Our technique eliminates ambiguities that commonly occur on tiled displays. It improves the usability of multi-monitor systems by virtually eliminating the bezels. We describe a setup and provide results from an evaluation experiment conducted on a 3x3 and on a 10x5 tiled display wall.</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_CALLIT2&diff=3884 2009-10-27T15:32:08Z

<p>Andrew Forsberg: added agenda times for calit2 visit, discussing display/projection alternatives</p> <hr /> <div>==50K-view question:==<br /> *For each Calit2 display, make notes about how it compares to the __immersive experience__ of the 1998 Brown Cave? (seams? head-tracked viewing? working volume size? tracking quality?)<br /> <br /> ==Alternative displays &amp; projection material==<br /> *general discussion on this, commercial TV's come and go quickly..<br /> *Are mfgt's thinking about tiling their displays &amp; getting rid of borders?<br /> *LG borderless display (http://www.electronichouse.com/article/lg_introduces_frameless_plasma_tv/)<br /> *projecting on bezels ([[PrePrint: Tiled++: An Enhanced Tiled Hi-Res Display Wall]])<br /> *when will new LCD displays be available for purchase?<br /> <br /> ==Screens:==<br /> *How visible are the seams<br /> *are the seams better/worse than vignetting<br /> *How much more distorted will the image be for non tracked users<br /> *How does the transition from wall to floor look<br /> *how are the screens attached to the frame<br /> *how rigid are the screens, is there any sway<br /> *Do they have problems keeping them clean<br /> *Are they prepared if a screen is damaged, needs replacement<br /> ==Projectors:==<br /> *How well aligned are the projectors to the screens<br /> *How well are the projector pairs aligned to each other<br /> *How far away are the projectors (projector throw)<br /> *Do they do any type of projector blending<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == Color Balance: ==<br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3883 2009-10-20T15:40:16Z

<p>Andrew Forsberg: /* Software: researcher/developer tools */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> * [[Vis 2009 discussion dfk/dhl/asf]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3882 2009-10-20T15:34:34Z

<p>Andrew Forsberg: /* Upcoming Trip to Californina */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALLIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3881 2009-10-20T15:34:17Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> === Upcoming Trip to Californina ===<br /> *[[Agenda and action items for Disney Imagineering]]<br /> *[[Agenda and action items for CALIT2]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_CALLIT2&diff=3880 2009-10-20T15:33:43Z

<p>Andrew Forsberg: </p> <hr /> <div>==50K-view question:==<br /> *For each Calit2 display, make notes about how it compares to the __immersive experience__ of the 1998 Brown Cave? (seams? head-tracked viewing? working volume size? tracking quality?)<br /> <br /> ==Screens:==<br /> *How visible are the seams<br /> *are the seams better/worse than vignetting<br /> *How much more distorted will the image be for non tracked users<br /> *How does the transition from wall to floor look<br /> *how are the screens attached to the frame<br /> *how rigid are the screens, is there any sway<br /> *Do they have problems keeping them clean<br /> *Are they prepared if a screen is damaged, needs replacement<br /> ==Projectors:==<br /> *How well aligned are the projectors to the screens<br /> *How well are the projector pairs aligned to each other<br /> *How far away are the projectors (projector throw)<br /> *Do they do any type of projector blending<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == Color Balance: ==<br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_Disney_Imagineering&diff=3879 2009-10-20T15:33:18Z

<p>Andrew Forsberg: </p> <hr /> <div>Here are just some of the questions we should ask when visitng Disney Imagineering:<br /> <br /> (Please be sure to carefully run through all of these top-to-bottom.)<br /> <br /> == Color Balance: ==<br /> <br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == Tiling: ==<br /> <br /> *How well are the displays tiled, is there any gap, or do they overlap<br /> *At what angle are the discreet tiles visible. <br /> *How large of an area is the &quot;sweet spot&quot;<br /> <br /> ==Screen: ==<br /> <br /> *How much does the curved screen affect the projection<br /> *Is the screen they use better/worse than the provided screen<br /> *How is the screen attached<br /> <br /> == TV: ==<br /> <br /> *How was the screen removed, and do you gain pixels by removing it<br /> *Is the display still stable with he screen removed<br /> *How is the system mounted into the frame<br /> *How do they compensate for the bezel at the bottom<br /> *Have they had any significant hardware failures<br /> *Can a system be easily replaced if it dies<br /> *Want to see display running is stereo, so we can witness non-sync<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *What is the list of other software options did they consider? (VR Juggler? Others?)<br /> *How are the computers tied together, any special networking? What is latency?<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> == 3D Tracking: ==<br /> *Document the pros/cons of each 3D tracking system<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?<br /> <br /> ==Audio:==<br /> *What audio system is being used? (3D spatialized?)<br /> *How is audio synchronized with visuals? What software?<br /> <br /> ==Haptics:==<br /> *Is there haptics input/output support?<br /> <br /> == Stereo display: ==<br /> *What is the list of work that would make stereo display work? Which are understood and which need research/solutions?<br /> <br /> ==Extras:==<br /> *What are the using for input/control?<br /> *Do they use any type of tracking<br /> *what stereo glasses do they use</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_CALLIT2&diff=3878 2009-10-20T15:32:31Z

<p>Andrew Forsberg: </p> <hr /> <div>==50K-view question:==<br /> *For each Calit2 display, make notes about how it compares to the __immersive experience__ of the 1998 Brown Cave? (seams? head-tracked viewing? working volume size? tracking quality?)<br /> <br /> ==Screens:==<br /> *How visible are the seams<br /> *are the seams better/worse than vignetting<br /> *How much more distorted will the image be for non tracked users<br /> *How does the transition from wall to floor look<br /> *how are the screens attached to the frame<br /> *how rigid are the screens, is there any sway<br /> *Do they have problems keeping them clean<br /> *Are they prepared if a screen is damaged, needs replacement<br /> ==Projectors:==<br /> *How well aligned are the projectors to the screens<br /> *How well are the projector pairs aligned to each other<br /> *How far away are the projectors (projector throw)<br /> *Do they do any type of projector blending<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> == Color Balance: ==<br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> == Tracking: ==<br /> *Rate each 3D tracking system (camera, other?). Would it work well for CavePainting, ADVISER, CaveWriting, etc.?</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_Disney_Imagineering&diff=3877 2009-10-20T15:27:49Z

<p>Andrew Forsberg: </p> <hr /> <div>Here are just some of the questions we should ask when visitng Disney Imagineering:<br /> <br /> (Please be sure to carefully run through all of these top-to-bottom.)<br /> <br /> == Color Balance: ==<br /> <br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == Tiling: ==<br /> <br /> *How well are the displays tiled, is there any gap, or do they overlap<br /> *At what angle are the discreet tiles visible. <br /> *How large of an area is the &quot;sweet spot&quot;<br /> <br /> ==Screen: ==<br /> <br /> *How much does the curved screen affect the projection<br /> *Is the screen they use better/worse than the provided screen<br /> *How is the screen attached<br /> <br /> == TV: ==<br /> <br /> *How was the screen removed, and do you gain pixels by removing it<br /> *Is the display still stable with he screen removed<br /> *How is the system mounted into the frame<br /> *How do they compensate for the bezel at the bottom<br /> *Have they had any significant hardware failures<br /> *Can a system be easily replaced if it dies<br /> *Want to see display running is stereo, so we can witness non-sync<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *What is the list of other software options did they consider? (VR Juggler? Others?)<br /> *How are the computers tied together, any special networking? What is latency?<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> ==Audio:==<br /> *What audio system is being used? (3D spatialized?)<br /> *How is audio synchronized with visuals? What software?<br /> <br /> ==Haptics:==<br /> *Is there haptics input/output support?<br /> <br /> == Stereo display: ==<br /> *What is the list of work that would make stereo display work? Which are understood and which need research/solutions?<br /> <br /> ==Extras:==<br /> *What are the using for input/control?<br /> *Do they use any type of tracking<br /> *what stereo glasses do they use</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Agenda_and_action_items_for_Disney_Imagineering&diff=3876 2009-10-20T15:16:32Z

<p>Andrew Forsberg: </p> <hr /> <div>Here are just some of the questions we should ask when visitng Disney Imagineering:<br /> <br /> == Discussion points: ==<br /> *What is the list of work that would make stereo display work? Which are understood and which need research/solutions?<br /> <br /> == Color Balance: ==<br /> <br /> *I would like to look at color balance adjustments<br /> *Are they using any type of aid to adjust color balance<br /> <br /> == Tiling: ==<br /> <br /> *How well are the displays tiled, is there any gap, or do they overlap<br /> *At what angle are the discreet tiles visible. <br /> *How large of an area is the &quot;sweet spot&quot;<br /> <br /> ==Screen: ==<br /> <br /> *How much does the curved screen affect the projection<br /> *Is the screen they use better/worse than the provided screen<br /> *How is the screen attached<br /> <br /> == TV: ==<br /> <br /> *How was the screen removed, and do you gain pixels by removing it<br /> *Is the display still stable with he screen removed<br /> *How is the system mounted into the frame<br /> *How do they compensate for the bezel at the bottom<br /> *Have they had any significant hardware failures<br /> *Can a system be easily replaced if it dies<br /> *Want to see display running is stereo, so we can witness non-sync<br /> <br /> ==Computer/Software:==<br /> *What software are they using to drive the displays<br /> *What other software options did they consider?<br /> *How are the computers tied together, any special networking<br /> *What computer configuration are they using<br /> *What graphics cards<br /> *What OS<br /> <br /> ==Extras:==<br /> *What are the using for input/control<br /> *Do they use any type of tracking<br /> *what stereo glasses do they use</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=VRG3D_Requirements&diff=3867 2009-10-19T13:08:40Z

<p>Andrew Forsberg: New page: == VRG3D Requirements == * documentation ** &quot;make doc&quot; makes doxygen style documentation ** it&#039;s possible to make introduction page... * examples ** lowest-level events * have short-term ...</p> <hr /> <div><br /> == VRG3D Requirements ==<br /> * documentation<br /> ** &quot;make doc&quot; makes doxygen style documentation<br /> ** it's possible to make introduction page...<br /> * examples<br /> ** lowest-level events<br /> * have short-term milestones &amp; then get guinea pigs to test it (is it actually easy to use?)<br /> * synching<br /> * interaction<br /> * 3D graphics<br /> * multiple displays<br /> * multiple OS's<br /> * testability<br /> * &quot;easy-of-use&quot;<br /> * code repository &amp; code access</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3866 2009-10-19T13:07:37Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Software: commercial quality === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software: researcher/developer tools ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3865 2009-10-19T13:06:49Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> <br /> === Software tools for developers ===<br /> <br /> * [[Cave Software Overview]]<br /> * [[VRG3D Requirements]]<br /> <br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3864 2009-10-19T13:05:06Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph, ParaView)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> [[Cave Software Overview]]<br /> <br /> === Software tools for developers ===<br /> <br /> * [[VRG3D Information]]<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3859 2009-10-15T02:06:09Z

<p>Andrew Forsberg: /* Hardware supporting usability studies */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> * [[Action Items for Sept. 22nd, 2009]]<br /> * [[Action Items for Sept. 29th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** VRPN supports some GSR device -- Russ Taylor says to check with Mary Whitton to learn more<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> [[Cave Software Overview]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3801 2009-09-22T15:15:56Z

<p>Andrew Forsberg: </p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> ** Why is a projector-based system worse than HDTV approach?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> [[Cave Software Overview]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3800 2009-09-21T19:52:21Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === <br /> Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries ===<br /> Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Will commodity DLP projection technology work ===<br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF.<br /> Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === <br /> ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === <br /> Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == <br /> Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> [[Cave Software Overview]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3799 2009-09-21T19:50:55Z

<p>Andrew Forsberg: /* Will commodity DLP projection technology work */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Will commodity DLP projection technology work ===<br /> <br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Text with Checkerboard Stereo === <br /> Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> [[Cave Software Overview]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3798 2009-09-21T19:50:38Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Will commodity DLP projection technology work ===<br /> <br /> * Problem: Are commodity DLP projection technologies high-enough quality &amp; reliable for a next-gen Cave?<br /> * Input needed<br /> ** An understanding of how much effort Mark Mine et al. at Disney have put in<br /> ** What is Mark's estimate on how much more time/effort it will take to have a high-quality display<br /> ** standard desktop text does not look good on Mitsubishi HDTVs. Is that a &quot;show stopper&quot;?<br /> * Experiments needed<br /> ** ?<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> [[Cave Software Overview]]<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3786 2009-09-18T16:26:56Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> &lt;br&gt;<br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> &lt;br&gt;<br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3785 2009-09-18T16:26:31Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> &lt;br&gt;<br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3784 2009-09-18T16:26:18Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> * Problem: What are the consequences of tiling displays together?<br /> * Input needed<br /> ** Expert feedback from sites with tiled displays like the ones we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Setup 2 displays and report on artifacts at edge between them (color, geometry)<br /> * Decision: ?<br /> <br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> * Input needed<br /> ** Expert feedback from sites already experimenting with the displays we'll use (Calit2, Disney, KAUST)<br /> * Experiments needed<br /> ** Compare visual angle of smallest comfortable text on desktop display versus on checkerboard stereo display.<br /> * Decision: ?<br /> <br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Problem: Would camera-based tracking be a value or time-sink for the Cave?<br /> * Input:<br /> ** Talk with people using camera-based tracking (Calit2, Disney, KAUST, Lit3D, Iowa State, UNC?, ..)<br /> * Experiments needed:<br /> ** Try first hand most promising camera-based tracking and document:<br /> *** the degree to which it is: wireless, accurate, low-latency, unobtrusive<br /> *** the degree to which it provides: head-tracking, wand-tracking, tracking of fingers/feet/body, tracking of &quot;phicons&quot;/props<br /> * Decision: ?<br /> <br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> * Experiments:<br /> ** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> ** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3783 2009-09-18T16:15:29Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> <br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Goals: wireless, accurate, low-latency, unobtrusive<br /> * Examples: head-tracking, tracking fingers and body, tracking &quot;phicons&quot;/props<br /> * Q: Is camera-based tracking reliable in a Cave?<br /> <br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> ** Case studies we'd like a turn-key software for:<br /> *** try visualizing Leopold Grinberg's arterial branch dataset (we don't have easy tool for it right now, but want one!)<br /> *** &lt;&lt; who else on campus has wanted to visualize data but we didn't have a tool to do it-- use as case study &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=New_CAVE_Design&diff=3782 2009-09-18T16:13:59Z

<p>Andrew Forsberg: /* Initial Design Issues */</p> <hr /> <div>=Hept-Cave Design Wiki=<br /> <br /> 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.<br /> <br /> == Weekly Cave action items ==<br /> Below is a list of action items for each Cave design meeting.<br /> * [[Action Items for Sept. 15th, 2009]]<br /> <br /> == Initial Design Issues ==<br /> <br /> === Display Surface Angles === Assigned to DHL. Updates are due by 12:00 noon on 9/14.<br /> <br /> * Problem: What are the consequences of display surface angles and/or curvature (horizontal and vertical angles may be different)?<br /> * Input needed<br /> ** Expert feedback from Acevedo re KAUST design choices<br /> * Experiments needed<br /> ** Set up two side-by-side and top/bottom displays and evaluate anecdotally<br /> * Decision: ?<br /> <br /> === Blending/Butting at Display Boundaries === Assigned to SGF. Updates are due on 9/14 by 12:00 noon<br /> <br /> === Text with Checkerboard Stereo === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * 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?<br /> <br /> === Floor Design === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Treadmill Options === ( not Omni-directional) Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Fixed wall design, or can it unfold into a powerwall? === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Ceiling Value, and Design Options === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> === Contracting to an Integrator === Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: Would contracting to an integrator to build based on an RFP be effective?<br /> * Input:<br /> ** Phone feedback from some of the potential integrators<br /> * Decision:<br /> <br /> === [[3D Tracking options]] === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> * Goals: wireless, accurate, low-latency, unobtrusive<br /> * Examples: head-tracking, tracking fingers and body, tracking &quot;phicons&quot;/props<br /> * Q: Is camera-based tracking reliable in a Cave?<br /> <br /> === Hardware supporting usability studies === Assigned to ASF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: is special hardware needed to support evaluation of Cave-like systems (e.g., devices that measure galvanic skin response (GSR))?<br /> * Input needed<br /> ** Advice from Mel Slater (How does Mel decide when GSR, etc. is important? How expensive is the system?)<br /> ** Mel says, &quot;[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.&quot;.<br /> ** Consider whether results from future (or past) studies would be significantly improved with such devices?<br /> *** asf thoughts (may be wrong!): GSR helps detects changes in a person's &quot;comfort&quot;-- 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.<br /> * Experiments needed<br /> ** none<br /> * Decision: ?<br /> <br /> === Commercial Software Availability === Assigned to JH. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> * Problem: What do we need to do to make sure that commercial software will be usable in our new facility?<br /> * Input:<br /> ** Feedback from some of the software players (Avizo/Amira, Ensight, OpenSceneGraph)<br /> ** Case studies we'd like a turn-key software for:<br /> *** try visualizing Leopold Grinberg's arterial branch dataset<br /> *** &lt;&lt; if other groups on campus have asked to visualize data &amp; we did not have a way, include that kind of data in a test. &gt;&gt;<br /> * Decision:<br /> <br /> == Schedule, Timeline, and Deliverables == Assigned to SGF. Updates are due by 12:00 noon on Monday, 9/14.<br /> <br /> The following describes our schedule, timeline, and<br /> deliverables using absolute months into the project (months 0-11 is year 1, months 12-23 is year 2, etc.).<br /> <br /> == Year 1 (0.50 hw-person FTE +consulting) ==<br /> <br /> We will finalize hardware decisions which will<br /> involve evaluating changes in availability since proposal submission; demonstrations of competing manufacturer’s<br /> equipment; consultation regarding details of acquiring, machining, and integrating elements; and<br /> ordering the central display equipment (projectors, screen material, computers, trackers). The new equipment<br /> will be received late in the year. Through a process that minimizes system downtime, the 1998 Cave<br /> will be taken down and removed.<br /> <br /> * Acquire test projection system(s) (month 1)<br /> * Acquire test graphics system(s) (month 1)<br /> * Acquire test tracking system(s) (month 1)<br /> * multi-site visit, design discussions, consultent visits (month 1 - month 3)<br /> * finalize refined design (due month 3, 1.5 hw-person mos)<br /> * order additional wall/test equipment (month 2)<br /> * Begin build on test tiled display wall (month 3 - month 6, 1.0 hw-person mo)<br /> * 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.<br /> * receive equipment (due month 8, 0.5 hw-person mos)<br /> * 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<br /> * raised floor and other site preparations complete (due month 11, 1.0 hw-person mo)<br /> * Install replacement tile wall, temporary system (month 11)<br /> * remove 1998 Cave (due at least disruptive time in year 1 TBD, 0.5 hw-person mo)<br /> <br /> == Year 2: (0.67 hw-person FTE, 0.58 swe-person FTE)==<br /> In year 2 we will complete construction of the<br /> display, bring computer systems online, install TGS’s Avizo and our own VRG3D software, and begin<br /> testing individual and linked systems.<br /> * 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<br /> * display-computer interconnect (due month 20, 0.5 hw-person mo)<br /> * tracker system(s) (due month 20, 2-4 hw-person mos) install and test; calibrate; create hooks for monitoring and testing<br /> * 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<br /> * install Avizo (due month 23, 1 swe-person mos)<br /> == Year 3 (0.63 hw-person FTE, 0.63 swe-person FTE) ==<br /> Monitoring and testing reliability software will be<br /> designed, developed, and deployed. Application users and developers will be able to begin using the system.<br /> * VRG3D-based example application (due month 26, 2 swe-person mos) identify additional problems with library<br /> * distribution version of VRG3D available (due month 30, 1 swe-person mos)<br /> * application users can now begin creating new applications<br /> * 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)<br /> <br /> == Year 4 (0.17 hw-person FTE, 0.33 swe-person FTE) == <br /> In year 4 we will finalize the software infrastructure,<br /> complete the auto-calibration system.<br /> * software library changes (due month 36, 2 hw-person mos, 3 swe-person mos)<br /> (note that these are not maintenance, but part of the development process); feature request from<br /> specific application areas; application users will change apps to use them<br /> * final software distributions to SourceForge (due month 47, 1 swe-person mos)</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Wrists&diff=3781 2009-09-18T16:09:53Z

<p>Andrew Forsberg: /* Tools */</p> <hr /> <div>The wrist is a diarthrodial anatomical joint consisting of 8 small bones (scaphoid, capitate, hamate, lunate, trapezium, trapezoid, triquetrum, pisiform) and 7 long bones (radius, ulna, and 5 metacarpals). When subject to injury and disease the wrist undergoes changes in kinematics, inter-bone joint space areas, cartilage thickness, length of ligament paths, etc. Developing computational tools for the analysis of anatomical joint characteristics is important in understanding the cause of injury, tracing the progress of disease, and taking preventative measures. <br /> <br /> &lt;gallery widths=&quot;250px&quot; heights=&quot;250px&quot;&gt;<br /> Image:Wrist.jpg.jpeg| X-ray of the wrist with bone names<br /> Image:Ligaments.jpg| Ligaments: posterior view of left wrist<br /> &lt;/gallery&gt;<br /> <br /> <br /> ==Description of Overall Pipeline==<br /> <br /> #[[Data]] <br /> #[[Bone Surface Extraction]]<br /> #[[Registration of Bones Across Positions]]<br /> #[[Retrieval of Kinematics]]<br /> #[[Inter-bone Joint Space Area Calculations]]<br /> #[[Ligament Path Calculations]] <br /> #[[Cartilage Maps (location &amp; thickness)]]<br /> #[[Cartilage Surface Deformations]]<br /> #[[Joint Simulation]]<br /> <br /> ==Specific Tools and Technical Details==<br /> <br /> #[[registration]]<br /> #[[joint space area calculations]]<br /> #[[cartilage building]]<br /> #&quot;wiggling&quot; bones around<br /> #ligament length measures<br /> <br /> [[Wrist Pipeline Technical Details | Technical Details on Wrist Pipeline and its relationship to the $G software framework]]</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Wrists&diff=3780 2009-09-18T16:09:39Z

<p>Andrew Forsberg: /* Non-Technical Description of Overall Pipeline */</p> <hr /> <div>The wrist is a diarthrodial anatomical joint consisting of 8 small bones (scaphoid, capitate, hamate, lunate, trapezium, trapezoid, triquetrum, pisiform) and 7 long bones (radius, ulna, and 5 metacarpals). When subject to injury and disease the wrist undergoes changes in kinematics, inter-bone joint space areas, cartilage thickness, length of ligament paths, etc. Developing computational tools for the analysis of anatomical joint characteristics is important in understanding the cause of injury, tracing the progress of disease, and taking preventative measures. <br /> <br /> &lt;gallery widths=&quot;250px&quot; heights=&quot;250px&quot;&gt;<br /> Image:Wrist.jpg.jpeg| X-ray of the wrist with bone names<br /> Image:Ligaments.jpg| Ligaments: posterior view of left wrist<br /> &lt;/gallery&gt;<br /> <br /> <br /> ==Description of Overall Pipeline==<br /> <br /> #[[Data]] <br /> #[[Bone Surface Extraction]]<br /> #[[Registration of Bones Across Positions]]<br /> #[[Retrieval of Kinematics]]<br /> #[[Inter-bone Joint Space Area Calculations]]<br /> #[[Ligament Path Calculations]] <br /> #[[Cartilage Maps (location &amp; thickness)]]<br /> #[[Cartilage Surface Deformations]]<br /> #[[Joint Simulation]]<br /> <br /> ==Tools==<br /> <br /> #[[registration]]<br /> #[[joint space area calculations]]<br /> #[[cartilage building]]<br /> #&quot;wiggling&quot; bones around<br /> #ligament length measures<br /> <br /> [[Wrist Pipeline Technical Details | Technical Details on Wrist Pipeline and its relationship to the $G software framework]]</div>

Andrew Forsberg http://vrl.cs.brown.edu/wiki/index.php?title=Wrists&diff=3768 2009-09-16T17:48:28Z

<p>Andrew Forsberg: /* Tools */</p> <hr /> <div>The wrist is a diarthrodial anatomical joint consisting of 8 small bones (scaphoid, capitate, hamate, lunate, trapezium, trapezoid, triquetrum, pisiform) and 7 long bones (radius, ulna, and 5 metacarpals). When subject to injury and disease the wrist undergoes changes in kinematics, inter-bone joint space areas, cartilage thickness, length of ligament paths, etc. Developing computational tools for the analysis of anatomical joint characteristics is important in understanding the cause of injury, tracing the progress of disease, and taking preventative measures. <br /> <br /> &lt;gallery widths=&quot;250px&quot; heights=&quot;250px&quot;&gt;<br /> Image:Wrist.jpg.jpeg| X-ray of the wrist with bone names<br /> Image:Ligaments.jpg| Ligaments: posterior view of left wrist<br /> &lt;/gallery&gt;<br /> <br /> <br /> ==Non-Technical Description of Overall Pipeline==<br /> <br /> #[[Data]] <br /> #[[Bone Surface Extraction]]<br /> #[[Registration of Bones Across Positions]]<br /> #[[Retrieval of Kinematics]]<br /> #[[Inter-bone Joint Space Area Calculations]]<br /> #[[Ligament Path Calculations]] <br /> #[[Cartilage Maps (location &amp; thickness)]]<br /> #[[Cartilage Surface Deformations]]<br /> #[[Joint Simulation]]<br /> <br /> ==Tools==<br /> <br /> #[[registration]]<br /> #[[joint space area calculations]]<br /> #[[cartilage building]]<br /> #&quot;wiggling&quot; bones around<br /> #ligament length measures<br /> <br /> [[Wrist Pipeline Technical Details | Technical Details on Wrist Pipeline and its relationship to the $G software framework]]</div>

Andrew Forsberg